Skip to main content
Skip table of contents

DOI Fabrica: Web Interface

Your test ( and production ( Fabrica account userIDs are the same with different prefixes assigned.

Keep in mind that DataCite’ test system is completely separate from production.

Accessing DataCite Fabrica


  • Repository account ID

  • The Repository Account ID is the username. Your account ID is the same for test and production Fabrica. Your DOI contact should have received these details from ARDC.  If you don’t have this information, contact your  DOI contact or email

  • Password

  • You have different passwords in test and production Fabrica.  

    Your organisation's nominated system email should have received a link from Fabrica to assign a password.  Get in touch with your organisation's DOI contact for the password.

    As it is now, your repository accountID and password are shared among all the users within the organisation’s DOI users.

  • If you are also using the DOI API, your Fabrica password is your API password

  • Keep in mind that by resetting your Fabrica password you will be also resetting the password used by the DataCite APIs (i.e. REST, MDS and EZ APIs)

Login procedure

  1. Go to  (test:

  2. Click on the upper right hand corner of the screen and enter your account ID and password

  3. Once logged in, you will be presented with your Repository Dashboard which gives you:

  • the account information overview which includes the name of the Repository and the total number of DOIs.

  • repository settings 

  • the prefix(es) assigned to your repository

  • list of all DOIs minted by the repository

The way the DataCite Fabrica system works is that there is no way to edit or update the organisation name or repository ID once it’s created. If there is a valid business need to change the organisation member ID and/or repository ID, the only way to do this is by creating  a new repository under a new  consortium organisation. DataCite would then transfer the DOIs and prefix from the old repository to the newly created account. Send an email to if you require a change in account ID.

You, however, can change your repository name when you are logged in to Fabrica.


Minting DOIs

Organisations are required to provide the minimum metadata requirements to mint a DOI. Below are the required metadata fields:

  • URL - The URL for the landing page of the dataset. 

  • Title - A name or title by which a resource is known.

  • Creators - The main researchers involved in producing the data, or the authors of the publication, in priority order.

  • Publisher - The holder of the data (including archives as appropriate) or institution that submitted the work.

  • Publication Year - The year when the data was or will be made publicly available.

  • ResourceType (with mandatory general type description sub property) - A description of the resource.

There are 2 ways to mint a DOI: 

Managing DOIs

  • Update a DOI: change your DOI metadata, including the URL; change the state of a DOI from Findable (equivalent to Active status) to Registered (equivalent to Inactive status);

  • Delete a draft DOI: draft DOIs have not been registered to the global handle system therefore these DOIs only exist at DataCite Fabrica and can be deleted.

  • DOI states explained: understand the 3 DOI states: Draft, Registered and Findable


DOI Broken Link Check

DataCite has a link checker service that periodically checks a random sampling of DOIs to verify that they still resolve to a valid URL and to gather other useful information about the metadata for DOIs registered with DataCite.

The link checker service runs automatically in the background, so there is nothing Members need to do and nothing they need to enable in order to benefit from the service.

The results of the link checker are displayed in DOI Fabrica at the bottom of each DOI record that has been checked.

Below is an example of a link checker result for one of the DOIs minted by ARDC:



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.