LogoLogo
  • Getting Started with FAIRsharing
  • Alignment with Community Efforts
  • FAIRsharing Data Access
  • Attribution for you
  • About Our Records
    • Record Icons
    • Relation Graphs
    • Record Actions
  • Updating Your Record
    • How to Update a Record
    • General Information
      • Record Name and Logo
      • Abbreviation
      • Homepage
      • Year of Creation
      • Countries
      • Registry Type
      • Status
      • Identifier Type
      • Description
      • Contact Information
      • Object Types
      • Subjects, domains, taxonomies and user-defined tags
    • Licences and Support Links
      • Licences
      • Support Links
    • Publications
    • Organisations and Grants
      • Importing ROR Organisations
      • Organisation Name
      • Organisation URL
      • Organisation Type
      • Countries
      • Type of Relationship
      • Leading Organisations
      • Grant
  • Relations to Other Records
    • From Standards Records
    • From Database Records
    • From Data Policy Records
    • From FAIRassist Records
    • From Collections
    • From Organisations
  • Additional Information
    • Associated Tools
    • Certification and Community Badges
    • Cross References
    • Data Processes
    • Database Conditions
    • Policy Content and Scope
  • How To
    • Unsure where to start?
    • Searching and Browsing
      • Search
      • Advanced Search
      • Database Discovery
      • Browse Subjects
  • Community Champions
    • Thinking of Joining Us?
    • Welcome!
    • About Community Curation
      • Email Templates
Powered by GitBook
On this page

Was this helpful?

  1. Relations to Other Records

From Database Records

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

FAIRsharing mandates that each database record provide the type of identifier(s) it mints for its content in one of two ways, either:

  1. add the standardised persistent identifier schema (e.g. DOI, ARK) to your record via the Relationships tab with the implements relationship type, or

  2. tick the box in the General Information tab that confirms that the database uses an internal identifier schema instead of a standardised one. More information is available in our identifier type documentation.

It is recommended that you add relationships to any formats and terminologies that your database utilises; most often this is done through the use of outputs or related to relationships, though others may be appropriate.

Please add any other relationships that this database has with other resources registered in FAIRsharing.

Please also see the general information regarding our minimal curation requirements.

FAIRsharing record relationships allow you to enumerate all of the ways in which your database is related to other resources within the wider ecosystem of research standards, databases, policies and FAIR assistance components. 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.

Full list of database relationships

This table summarises only those relationships available from within Database records. Other documentation in this section covers standards, data policies, FAIRassist records, 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

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

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 of the same type

The linked resource has been retired as it is no longer active or actively maintained

RELATED DATABASES

recommends

any policy to any database, standard, or FAIRassist record

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, policy, or FAIRassist record

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. As the maintainer of a record, choose the level of detail that best expresses the relationships your resource has with the wider research landscape.

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.

PreviousFrom Standards RecordsNextFrom Data Policy Records

Last updated 14 days ago

Was this helpful?

Any database to any standard; unless your database uses internal identifiers, at least one implements relationship to an must be used to show the type of persistent identifier(s) your database utilises.

This database shares a portion of code with another database, e.g. the repositories.

identifier schema
Dataverse