Alignment of FAIRsharing Policy Metadata / FAIRsFAIR Structured Policy Description Template / RDA Policy WG Elements

	A	B	C	D	E	G	H	I	K	L
1	CC BY 4.0 Lister, A., & Davidson, J. (2024). Alignment of FAIRsharing Policy Attributes with Community Efforts (1.0.0). Zenodo. https://doi.org/10.5281/zenodo.10658162			Please see our related blog posts at: https://blog.fairsharing.org/?p=691 https://dcc.ac.uk/blog/fairsharing-and-dcc-collaborate-align-policy-metadata https://blog.fairsharing.org/?p=451
2	FAIRsFAIR Structured Policy Description Template (Step by step guide) (checklist) Davidson et. al			Match type with FAIRsharing metadata (see FAIRsharing documentation)	FAIRsharing metadata fields	Concordat on Open Research Data (hosted by UKRI)	Match type with FAIRsharing metadata (see FAIRsharing documentation)	FAIRsharing metadata fields	RDA: Developing a Research Data Policy Framework for All Journals and Publishers Hrynaszkiewicz et. al. This document deals more with the content of a policy than its context, and therefore will necessarily not completely match Davidson et. al or FAIRsharing.	General Comments
3	Number	Section	Policy Element			Number and Policy Element			Policy element

4	1	Policy Context	Title of policy	exact	Record name
5	2		Availability of the policy	exact	presence within FAIRsharing will provide both human- and machine-readable metadata
6	3		Country/Countries	exact	Countries
7	4		Year policy was introduced	exact	Year of creation
8	5		Status of policy	exact	status
9	6		Policy is scheduled for review	not in initial mapping	n/a					This level of detail is not required for FAIRsharing at this stage.
10	7		If scheduled for review, when will this take place?	not in initial mapping	n/a					This level of detail is not required for FAIRsharing at this stage.
11	8		Persistent Identifier (PID) for policy (i.e., not a question about whether policy requires PIDs but rather is there a PID for the policy document itself)	exact	homepage					If a policy already has a persistent identifier, it must be provided in FAIRsharing through the FAIRsharing homepage field. Different policy document versions may be linked in the support information if desired, though version information is not required in FAIRsharing.
12	9		Policy is registered	exact	Registered with FAIRsharing and given a DOI					The record for the policy within FAIRsharing fulfils this requirement
13	10		Subject area/discipline covered	exact	subject, domain and taxonomy tags
14	11		Sub-discipline if applicable	exact	subject, domain and taxonomy tags
15	12		Type of policy	exact	record type					FAIRsharing has a subset of the ones available from the FAIRsFAIR forrm; FAIRsharing has journal (not in FAIRsFAIR), journal publisher, funder, project, society and institution.
16	13	Policy content	Scope of the policy	exact; but partial	FAIRsharing currently only stores data policies; however, our definition of "data" is very broad, and encompasses all digital research objects e.g. software, publications etc				Definition of research data	As FAIRsharing considers 'data' policies to cover all research digital objects, at the moment we have no scope beyond 'data. In future, we may add scope via the domain ontology.
17	14		Definition of data provided	not in initial mapping	n/a				Definition of research data	This level of detail is not required in FAIRsharing at this stage.
18	15		Sharing research software	exact, added in 2022	FAIRsharing: sharing research software				Supplementary materials	Hrynaszkiewicz et. al use this field to differentiate between the use of supplementary material vs the use of PIDs pointing to digital objects stored in a central repository of some kind. For Davidson et. al and FAIRsharing, this field is used to capture whether or not software is shared, and whether this is required or suggested. Not an exact match with Hrynaszkiewicz et. al, but definitely related.
19	16		Data sharing	exact, added in 2022	FAIRsharing: mandated data sharing	1a. Institutions should have policies, practices and culture that recognise the value of open data and of the work done to enable it throughout the research process.	exact	Mandated data sharing field may be anything other than 'not covered'	Mandatory data sharing (specific papers); Mandatory data sharing (all papers)
20	17		Alignment with FAIR principles	exact, added in 2024	Relationships from policy record to the FAIR Principles record (https://doi.org/10.25504/FAIRsharing.WWI10U).					This relationship was not explicitly stated until 2024, however it has always been available. Note that the relationship between the FAIR principles and a policy is added whenever a policy states even some degree of alignment with FAIR; it does NOT mean that the linked policy is in complete alignment with FAIR.
21	18		Metadata sharing	exact, added in 2022	FAIRsharing: sharing metadata	7p. Institutions should support provision of sufficient metadata for data evaluation and reuse.	exact	Sharing metadata field == yes
22	19		Exceptions to data sharing are allowed	exact, added in 2022	FAIRsharing: exceptions to data sharing	2c. Institutions should have verifiable and transparent processes of oversight to guide decisions on whether, when and how data may be made available in some form, to reflect situations where (e.g.) data relates to or is derived from individuals, or has commercial sensitivity, or third-party intellectual property rights.	exact	exceptions to data sharing == yes	Definition of exceptions; Embargoes
23	20		Policy includes expectation on data management planning (DMP) development	exact, added in 2022	FAIRsharing: DMP development (multiple fields)				Data Management Plans (DMPs)	The RDA item is specifically dealing with whether or not the DMP should be made public, and not about whether or not one should be made/versioned/produced at a particular stage. Therefore this is not directly analagous to any of the FAIRsFAIR items.
24	21		If a DMP should be developed, please indicate the stage at which it should be produced	exact, added in 2022	FAIRsharing: timing of DMP
25	22		Is there an expectation that the DMP will be updated and clearly versioned?	exact, added in 2022	FAIRsharing: updating of DMP
26	23		Policy makes reference to data protection (e.g, GDPR)	exact, added in 2022	FAIRsharing: data protection
27	24		Policy makes reference to research integrity	not in initial mapping	n/a				Peer review of data	This level of detail is not required in FAIRsharing at this stage.
28	25		Policy makes reference to specific standards or protocols that should be adopted.	exact	relationships from policy record to standards records	7q. Institutions should encourage the use of non-proprietary formats.	near match Although any explictly-mentioned standards will be recorded in the relationships within a FAIRsharing record, more general statements e.g. "non-proprietary formats should be used" cannot be captured in FAIRsharing metadata	Discover the recommended standards linked to the policy record	Data formats and standards
29	26		Use of trusted digital repositories	exact	relationships from policy record to database records	7o. Where institutions provide access to data repositories, these repositories should be able to guarantee the persistence of the datasets for a reasonable time period. See also item 32.	exact	Discover the recommended institutional database record via the policy's relationships, and check that database record's data preservation policy field.	Data repositories	The presence of relationship links to database records will provide "yes" answer to this question without stating if those resources are required or recommended. As "trusted" is meant to be defined by the policymaker, this is not relevant to the FAIRsharing record and we deal with this item in the same way as item 25 (standards to be adopted)
30	27		Policy requires a data availability statement	exact, added in 2022	FAIRsharing: data availability statement				Data availability statements (DASs)
31	28		Policy addresses Intellectual Property (IP) rights	not in initial mapping	n/a					This level of detail is not required in FAIRsharing at this stage.
32	29		Policy specifies a preferred license type for outputs	exact, added in 2022	FAIRsharing: licence for outputs				Data licensing	Could also optionally provide the ability to explicitly list required/recommended licences. However, we will not implement this extra feature at this stage.
33	30		Policy includes expectation about data citation	exact, added in 2022	FAIRsharing: data citation	5j. Formal recognition should make use of responsible metrics for tracking research data use and impact, such as data citations. 8r. Where institutions provide access to data (and, where possible, software) repositories, these repositories should enable datasets and related software to be citable, for example by providing them with a persistent identifier.	5j: near match; FAIRsharing provides a field to say whether or not a clear statement and guidance around data citations are present, but FAIRsharing does not describe formal recognition around data citation. 8r: exact	Two routes: 1. (8r) Discover the recommended institutional database record via the policy's relationships, and check that database record's relationships to identifier schema format records 2. (5j, 8r) If data citation == 'yes', the policy provides a clear expectation about data citation.	Data citation
34	31		Policy specifies use of researcher identifier (e.g., ORCID)	exact	relationship to ORCID registry FAIRsharing record
35	32		Policy makes clear the minimum length of data availability beyond the life of the project (i.e., how long must the data be preserved)	exact, added in 2022	FAIRsharing: data preservation	8s. Institutional policies should require that data underpinning publications should as default be retained for at least ten years in a citable form. 7o. Where institutions provide access to data repositories, these repositories should be able to guarantee the persistence of the datasets for a reasonable time period. See also item 26.	near match In FAIRsharing, this value is 'yes' if the policy requires that selected data must be preserved for a set period of time. If the policy lacks clarity in relation to the preservation of selected data, or does not include such information at all, the value in this field is 'no'. Therefore a 'yes' value will not necessarily mean 10 years, but it does guarantee a set period of time, and therefore still useful here.	Data preservation == yes Discover the recommended institutional database record via the policy's relationships, and check that database record's data preservation policy field.
36	33	Support	Justified costs associated with RDM and making data FAIR are supported	exact, added in 2022	FAIRsharing: supported costs	3e. Institutions should acknowledge that infrastructure, training, staff support, and progress reviews for open and FAIR research have significant costs and they should have procedures in place to ensure funding of costs within the dual support system.	exact	Supported costs == yes		Funder policies only.
37	35		Guidance, training and/or support are provided to support compliance	exact, added in 2022	FAIRsharing: Compliance guidance	5h. Institutions should provide support (such as training, guidance, advice and policies) on legal, ethical, and professional frameworks of research integrity as related to issues of open data. This support should cover both appropriate citation and acknowledgement of others’ work, and provision of a preferred citation for underlying data and other relevant outputs including research software.	near match Compliance guidance in FAIRsharing is specifically about support for compliance with the data policy, which may be inferred to fit into 5h, 6n or 6l.	Compliance guidance == yes	Researcher/author support
38	35		Policy compliance is monitored	exact, added in 2022	FAIRsharing: compliance monitoring	10w. Institutions should undertake regular reviews to monitor their progress in implementing their responsibilities under the Concordat, register issues to be addressed, and identify and share best practice.	exact	Compliance monitoring == yes
39	36		Compliance is rewarded	not in initial mapping	n/a	9v. Institutions should support data science through skills development and career pathways. 5i. Institutional policies should recognise contributions to shared/open datasets in academic appointment, promotion, research assessment and research funding decisions.	not in initial mapping			Should be considered for inclusion within FAIRsharing.
40	9u					9u. Institutions should provide researcher training opportunities in an organised and professional manner.	not in scope			This level of detail is not required in FAIRsharing at this stage.
41	8t					8t. Institutions should provide guidance on relevant preservation policies and/or retention schedules.	not in initial mapping			This level of detail is not required in FAIRsharing at this stage.
42	6l					6l. Institutions should provide guidance to researchers throughout the research process on the correct and relevant data management and storage methodologies for that research field.	not in scope			This level of detail is not required in FAIRsharing at this stage.
43	1b	Infrastructure				1b. Institutions should provide appropriate access to infrastructure systems and services to enable their researchers to make research data open and usable.	not in scope			This level of detail is not required in FAIRsharing at this stage.
44	6k					6k. Institutions should provide access to the necessary infrastructure to enable researchers to manage their data effectively throughout the research process.	not in scope
45	6m					6m. Institutions should support and make use of shared research infrastructure.	not in scope
46	2d	Additional Restrictions on Open Data				2d. Institutional policies and guidance should acknowledge that on a case-by-case basis sharing be proportionate to the level of risk associated with the data.	not in scope
47	4g					4g. Data management plans should address embargo requests.	not in scope			While embargo periods are addressed in the 'exceptions to data sharing', and we do have fields relating to DMP development, we do not have a field covering that DMPs must address embargo requests.
48	4f					4f. Institutional research data policies must allow the possibility of an initial embargo period before data availability and reuse.	not in scope			While embargo periods are addressed in the 'exceptions to data sharing', all FAIRsharing requires is that any embargo information is clearly and explicitly stated; we do not store whether or not such embargos are allowed.
49	10x	Strategy				10x. Institutions should demonstrate a long-term commitment to open data.	not in scope
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100