From Database Records

A summary of all of the relations that you may use when editing a database record

This part of a FAIRsharing record allows you to create a rich list of standards, databases and policies that are related to your database. The corresponding Relation Graph for your record will not only showcase your resource's interoperability but also your collaborations and engagement with your community.

Our goal is to represent your database as accurately as possible, to showcase its attributes as well as its integration within the broader research landscape of standards, policies and other databases.

Do you mint persistent identifiers for the content of your database? This information is especially important within your FAIRsharing record. Please use the 'implements' relationship to show the type of identifier(s) you mint (e.g. DOI, ARK).

Full list of database record relationships

This table summarises only those relationships available from within Database records. Other documentation in this section covers standards, data policies, collections and organisations. The Display Location column below tells you where each relationship can be found in our record display.

You may also wish to review the types of databases available in FAIRsharing.

Label	Restrictions	Description	Display location
related_to	Any database to any standard or other database	This is our most generic relationship, and can be used between most record types. Use this if the more fine-grained relationships are not applicable.	RELATED STANDARDS or RELATED DATABASES
implements	Any database to any standard	This is our most generic database -> standard relationship. If your database uses a standard internally for some purpose, e.g. perhaps it utilises an RDF triplestore, but the other more precise relationships (accepts, outputs) are not suitable. Useful to e.g. standards developers, who want to know who is using their standard (even if only internally).	RELATED STANDARDS
accepts	Any database to any standard	Suitable for when a database accepts data that follows a particular standard. Such information is useful e.g. to researchers who need to know what standard to use so that they may deposit data with your database.	RELATED STANDARDS
outputs	Any database to any standard	Suitable for when a database outputs data that follows a particular standard	RELATED STANDARDS
extends	Any database to any other database	This is our most generic database -> database relationship. Useful when your resource extends a database, but other more precise relationships (shares_code_with, shares_data_with) are not suitable.	RELATED DATABASES
shares_code_with	Any database to any other database	This database shares a portion of code with another database, e.g. the Dataverse repositories.	RELATED DATABASES
shares_data_with	Any database to any other database	This database shares a portion of data with another database. This relation does not specify if the data being shared is from the resource you are editing, the resource being linked, or a combination of both.	RELATED DATABASES
deprecates	Any database to any other database	The linked resource has been retired as it is no longer active or actively maintained	RELATED DATABASES
recommends	Any policy to any database or standard	This relationship is not accessible from a database record; however, any policies that recommend your record will be automatically displayed.	IN POLICIES
collects	any collection to any database, standard, collection or policy	This relationship is not accessible from a database record; however, any collections that include your record will be automatically displayed.	IN COLLECTIONS

You may layer these relationships to more precisely describe what is available to your users. For instance, a database might both implement a particular format and also accept it. As the maintainer of a record, you can choose the level of detail; as with most FAIRsharing metadata, we are here to help you provide the level of detail that is most useful to your stakeholders. You can use the "related to" relationship, or can choose to itemise all or some of the different types of relationships you have with other resources; it's up to you.

Adding your record to a data policy that recommends it or a collection that collects it requires updates to that policy or collection; such edits cannot be performed in your own record. If you would like your record added to a policy or collection, please get in touch with our curation team.