This group is a follow-on group to the prior successful pilot led by the Resource Identification Initiative working group. The overarching goals of this WG are to develop a technical specification for the purposes of expanding and enabling a robust, community-wide implementation of an identifier strategy for research resources.
The Resource Identificaiton Initiative performed a pilot by prepending RRID to research resource identifiers so as to know that a research resource was used (see problem description here: https://peerj.com/articles/148/, and pilot summary here: http://f1000research.com/articles/4-134/v2). Issues with these types of identifiers and recommendations for identifier creation have been described recently in this 10-rules paper.
The scope of this working group is to define identifier behavior for material resources in the life sciences (eg. model organisms, cell lines, antibodies, and knockdown reagents)*. There are three scenarios:
- Resources are already identified by a single centralized nomenclature authority for the resource type
- Resources are already identified by several different nomenclature authorities that need to be coordinated
- Resources have not yet been given any (resolvable) identifiers at all
*Information resources like software are better suited to the Software Citation WG. Contribution of resources may be relevant to the Attribution WG.
Preliminary considerations for this group are:
- Format specification: e.g. can we assume the native CURIE from the sources (where available) would be prepended with RRID: ? (eg. RRID:MGI:12345)
- Coordination strategy for distributed sources; what are the criteria and how will the identifiers be registered as RRIDs?
- Creation/registration for new resource identifiers, coordination with nomenclature authorities
- Enhancement of JATS and/or creation of new citation type so that these can be referenced outside the paywall.
- Resolver specification
- Persistence in the face of source resources disappearing.
- Requirements for software tools for use by journals, users, repositories, OLNs, etc.
- Documentation for journals, users, repositories, OLNs, etc.
We anticipate a 6 month effort to define this specification.
GROUP EMAIL: email@example.com
Open for Group members only