+
+ )
+}
export default CoverageCard
diff --git a/templates/usrn/cards/index.js b/templates/usrn/cards/index.js
index 1836b135..f9d55c3b 100644
--- a/templates/usrn/cards/index.js
+++ b/templates/usrn/cards/index.js
@@ -1,3 +1,4 @@
export HeaderCard from './header-card'
+export CertificatesCard from './certificates-card'
export StatusCard from './status-card'
export StatusCardClosed from './status-card-closed'
diff --git a/templates/usrn/index.jsx b/templates/usrn/index.jsx
index 612c1091..1b61edbb 100644
--- a/templates/usrn/index.jsx
+++ b/templates/usrn/index.jsx
@@ -1,6 +1,11 @@
import React from 'react'
-import { HeaderCard, StatusCard, StatusCardClosed } from './cards'
+import {
+ HeaderCard,
+ CertificatesCard,
+ StatusCard,
+ StatusCardClosed,
+} from './cards'
import styles from './styles.module.css'
export const USRNTemplateActivated = ({
@@ -8,20 +13,26 @@ export const USRNTemplateActivated = ({
className,
tag: Tag = 'main',
...restProps
-}) => (
-
-
-
-
-)
+}) => {
+ const { template } = usrnParams
+
+ return (
+
+
+ {template === 'fair' && }
+
+
+ )
+}
export const USRNTemplateDeactivated = ({
+ usrnParams,
className,
tag: Tag = 'main',
...restProps
}) => (
-
+
)
diff --git a/texts/fair/certificates.yml b/texts/fair/certificates.yml
new file mode 100644
index 00000000..f1b85ae3
--- /dev/null
+++ b/texts/fair/certificates.yml
@@ -0,0 +1,22 @@
+typeCertificates:
+ - id: bronze
+ title: Bronze
+ isEnable: yes
+ description: |
+ Access to basic functionality of CORE services as they are.
+ accessText: |
+ You are a Starting member
+ - id: silver
+ title: Silver
+ isEnable: yes
+ description: |
+ Co-funds the maintenance of CORE services as they are.
+ accessText: |
+ You are a member
+ - id: gold
+ title: Gold
+ isEnable: yes
+ description: |
+ Co-funds the maintenance of CORE services and their continuous improvement.
+ accessText: |
+ You are a member
diff --git a/texts/fair/header.yml b/texts/fair/header.yml
index 7eb373e0..084f0406 100644
--- a/texts/fair/header.yml
+++ b/texts/fair/header.yml
@@ -1,7 +1,4 @@
-title: FAIR Report
+title: CORE FAIR certification
description: |
- This report aim to support the repositories in the USRN Discovery Pilot project to increase interoperability across the
- national and global repository network and establish a suitable institutional repository to be an "agency designated" (as
- defined by [the OSTP memo](https://www.whitehouse.gov/wp-content/uploads/2022/08/08-2022-OSTP-Public-Access-Memo.pdf) ) repository
- for federally funded research.
+ FAIR description
diff --git a/texts/fair/index.js b/texts/fair/index.js
index 96b55d2f..f589d7d3 100644
--- a/texts/fair/index.js
+++ b/texts/fair/index.js
@@ -1,5 +1,6 @@
import header from './header.yml'
+import certificates from './certificates.yml'
import status from './status.yml'
-export default { header, status }
-export { header, status }
+export default { header, certificates, status }
+export { header, certificates, status }
diff --git a/texts/fair/status.yml b/texts/fair/status.yml
index 378620e8..67f36034 100644
--- a/texts/fair/status.yml
+++ b/texts/fair/status.yml
@@ -1,340 +1,415 @@
-titleFirst: FAIR Report
+titleFirst: CORE FAIR certification report
descriptionFirst: |
- This report should give a live view of the status of the repository against a series of principles defined as
- [Desirable Characteristics of Digital Publication Repositories](https://sparcopen.org/wp-content/uploads/2022/10/Desirable-Characteristics-of-Digital-Publication-Repositories-APPROVED-20230331.pdf) and it should support and serve as a companion to the Toolkit created by the USRN Discovery project.
+ This report contain the estimation to what extent you correspond to the FAIR principles.
linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Toolkit
dateReport: Date of the last report update
buttons:
update: Update report
download: Download in PDF
statusItems:
- - id: freeAndEasy
+ - id: findable
isEnable: yes
type: text
- title: Free and Easy Discoverability & Access
+ title: Findable
description: |
- The repository provides broad, equitable, and maximally open access to
- resources and their metadata in both machine- and human-readable formats at no
- cost to users. This should be done in a timely manner after submission and with
- limited unscheduled downtime, consistent with legal and policy requirements.
- The repository’s content should be discoverable both within the repository
- (i.e., via a search interface) and externally (i.e., via discovery services and
- aggregators). The repository supports access to its content for persons with
- disabilities and adheres to current web accessibility standards. Provide an
- accessibility statement describing efforts to increase accessibility of the
- platform/content and how to seek help if an accessible version of a digital
- publication is not available.
+ The first step in (re)using data is to find them. Metadata and data should be easy to find for both humans and computers.
+ Machine-readable metadata are essential for automatic discovery of datasets and services, so this is an essential
+ component of the FAIRification process.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Free-and-Easy-Discoverability-and-Access
+ linkToolKit: 0
- id: repositoryOAIPMH
isEnable: yes
type: statistic
- title: Your repository supports OAI-PMH
- description: |
- The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in
- the remainder of this document) provides an application-independent interoperability
- framework based on metadata harvesting. This provides the basic building block to provide an
- interoperable digital publications repository.
- OAI-PMH is the most widely used protocol for exchanging information between repositories.
- It is the standard used by CERN, by arXiv, by Wikipedia, by repository software tools such as DSpace and ePrints, and by CORE.
-
- Repository managers can check their OAI-PMH endpoint using the [OAI-PMH Validator tool](https://www.openarchives.org/Register/ValidateSite).
-
+ title: Your repository supports OAI-PMH?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting.
+ This provides the basic building block to provide an interoperable digital publications repository.
- id: indexedContent
isEnable: yes
type: statistic
title: Indexed content
description: |
- The number of records CORE is able to index from your digital repository. If this number doesn't match your records
- it might mean you have issues in exposing your records in an interoperable way.
- The [Indexing status tab](/data-providers/{{ID}}/harvesting) provides a summary of any issue CORE finds while indexing your repository.
- A common issue is when institutions have more than one repository. CORE identifies some but not all of the repositories, which means the total number it identifies is less than the total in the repositories.
-
prefix: |
Number of metadata records:
- - id: accessFullTexts
+ - id: vocabulariesCOAR
isEnable: yes
type: statistic
- title: Access to full texts of research papers for your content
+ title: Do your metadata use COAR vocabularies
description: |
- The number of full text CORE is able to discover from your digital repository. You can check the [Harvesting tab](/data-providers/{{ID}}/harvesting) where we collect issues CORE discovered while indexing your repository.
- If this number doesn't match your records it might mean you have issues in exposing your records in an interoperable way.
- The [Indexing status tab](/data-providers/{{ID}}/harvesting) provides a summary of any issue CORE finds while indexing your repository.
- CORE requires that full text must be hosted on the same domain or subdomains as the OAI-PMH endpoint, unless we are informed by the institution about other owned domains containing full text.
-
+ More information about how to work towards this characteristic available on the USRN Discovery Toolkit.
+ recommendation: |
prefix: |
- Percentage of documents with access to full text:
- - id: clearUseGuidance
+ linkToolKit: https://zenodo.org/records/7108101
+ - id: applicationProfile
+ isEnable: yes
+ type: statistic
+ title: Your repository metadata supports a widely used Application Profile
+ description: |
+ Ensuring the usage of a well-known application profile means that the metadata of the publication is described in a less ambiguous and more accurate way.
+ Most used publications profiles are the OpenAIRE Guidelines 3.0+ and the RIOXX metadata application profile.
+ prefix: |
+ recommendation: |
+ CORE requires Dublin Core as a minimum; it supports OpenAIRE Guidelines; and it recommends RIOXX version 3.
+
+ CORE recommends that repositories use RIOXX v3, which we consider to be the most suitable metadata application profile
+ for describing scholarly research outputs. Rioxx: The Research Outputs Metadata Schema was developed
+ for institutional repositories to share metadata about the scholarly resources they contain.
+
+ Information about how to comply with metadata recommendation s are provided in the CORE Data Provider’s Guide.
+ ########################################################################################################################
+ - id: accessible
isEnable: yes
type: text
- title: Clear Use Guidance
+ title: Accessible
description: |
- The repository ensures metadata records for resources include licensing information
- stipulating reuse conditions. Ideally, machine-readable information on the OA
- status with the license is embedded in the resource.
- linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Clear-Use-Guidance
- - id: licensingMetadata
+ Once the user finds the required data, she/he/they need to know how they can be accessed,
+ possibly including authentication and authorisation.
+ - id: accessFullTexts
isEnable: yes
type: statistic
- title: Licensing
+ title: Do you provide access to full texts of research papers for your content?
description: |
- The percentage of metadata records with licence URLs CORE is able to recognise from the metadata.
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH
+ in the remainder of this document) provides an application-independent interoperability
+ framework based on metadata harvesting. Read more.
prefix: |
- Percent of metadata records with a licence specified:
+ Percentage of documents with access to full text:
recommendation: |
- Licensing and copyright information may be displayed in a machine-readable way, or by a text description.
- However, text descriptions such as “all rights reserved” may not be specific enough for other users to interpret.
- Much better is to provide a URL to the relevant Creative Commons licence, for example, for the non-commercial CC-BY licence, [https://creativecommons.org/licenses/by-nc/4.0/](https://creativecommons.org/licenses/by-nc/4.0/)
- By clicking on this link, a human can see the precise meaning of this licence. Any machine can identify immediately, and unambiguously, what kind of licence is stated.
-
- CORE promotes and advocates for the use of machine-readable licencing descriptions. In particular, we advise the use of the NISO Access License and Indicators (ALI) Schema.
-
- Institutions may have a blanket policy that covers all content with a specific publisher, which usually means that individual documents contain no licensing information. However, a specific CC-BY licence enables exceptions to be made for individual documents and reduces ambiguity.
-
- The CORE Rights Retention Statement tracker identifies with reasonable accuracy any specific licence conditions that are stated within an article or text file.
- - id: uniquePersistentIdentifiers
+ The data on this list is cached for performance reasons. Once you completed your work
+ please click here to refresh the cache. The processing will take some time
+ but you will be able to see the updated data
+ - id: embargoedDocuments
+ isEnable: yes
+ type: statistic
+ title: Do you label embargoed documents?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder
+ of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ prefix: |
+ Percentage of embargoed documents:
+ recommendation: |
+ ########################################################################################################################
+ - id: interoperable
isEnable: yes
type: text
- title: Unique Persistent Identifiers
+ title: Interoperable
description: |
- The repository assigns each resource a unique persistent identifier (PID),
- such as a digital object identifier (DOI), to support discovery, citation, reporting (e.g., of research progress),
- and research assessment (e.g., identifying the outputs of Federally funded research). The unique PID points to a
- persistent location that remains accessible even if the content is de-accessioned or no longer available.
- The repository supports PIDs for entities related to the resources, such as authors (e.g., ORCID), funders
- (e.g., Funder Registry), and organizations (e.g., ROR).
- linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Unique-Persistent-Identifiers
- - id: researchDatasets
- isEnable: no
+ The data usually need to be integrated with other data. In addition, the data need to interoperate
+ with applications or workflows for analysis, storage, and processing.
+ - id: signpostingFAIR
+ isEnable: yes
type: statistic
- title: Links to research datasets
+ title: Do you support FAIR Signposting?
description: |
- Links to research data are often shown with a URL, but much better is to use a persistent data identifier, such as a DOI,
- with the research data held in a trusted repository, which may be the same as your institutional repository,
- or may be a separate repository specifically for data, which is maintained by your repository team.
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document)
+ provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ recommendation: |
+ The data on this list is cached for performance reasons. Once you completed your work please click here to refresh the cache.
+ The processing will take some time but you will be able to see the updated data
+ linkDocumentation: 0
+ linkToolKit: 0
+ textToolKit: Link to documentation
prefix: |
+ - id: repositorySupportPersistent
+ isEnable: yes
+ type: statistic
+ title: Does your repository support persistent management of records?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document)
+ provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ recommendation: |
+ ########################################################################################################################
+ - id: reusable
+ isEnable: yes
+ type: text
+ title: Reusable
+ description: |
+ The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata
+ and data should be well-described so that they can be replicated and/or combined in different settings.
- id: accessibilityStatements
isEnable: yes
type: statistic
title: Do you provide data accessibility statements
description: |
- A data availability statement, also sometimes called a ‘data access statement’, tells the reader where the research
- data associated with a paper is available, and under what conditions the data can be accessed.
- They also include links where applicable to the data set.
- For example, the paper may state “The data that support the findings of this study are openly available in [repository name] at https://doi.org/[doi]”.
- This is in development right now.
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the
+ OAI-PMH in the remainder of this document) provides an application-independent interoperability
+ framework based on metadata harvesting. Read more.
- id: sourceCode
isEnable: yes
type: statistic
title: Do you provide links to source code
description: |
- This feature is currently under development.
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder
+ of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
prefix: |
- - id: doi
+ - id: recordsProvideAccessibility
isEnable: yes
type: statistic
- title: DOI
+ title: What proportion of your records provide data accessibility statements? (0-100%)
description: |
- The [DOI tab](/data-providers/{{ID}}/doi) provides a checklist of the number of content objects in your repository which have a DOI.
- It also identifies (and counts) the number of DOIs that it finds from articles held other repositories relating to research in your institution
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document)
+ provides an application-independent interoperability framework based on metadata harvesting. Read more.
prefix: |
- Percentage of metadata with DOI:
- - id: ORCID
+ ########################################################################################################################
+ - id: fitFunders
+ isEnable: yes
+ type: text
+ title: Fit for funders
+ description: |
+ The first step in (re)using data is to find them. Metadata and data should be easy to find
+ for both humans and computers. Machine-readable metadata are essential for automatic
+ discovery of datasets and services, so this is an essential component of the FAIRification process.
+ - id: datesOfDeposit
isEnable: yes
type: statistic
- title: ORCID
+ title: Do you expose metadata about dates of deposit?
description: |
- Public Investigator and Contributor Identifier is a non-proprietary alphanumeric code that uniquely identifies scientific authors.
- ORCID is an essential metadata tool that enables researchers to claim credit for their own research, without ambiguity.
- For example, there are many researchers with the common name “John Smith” or “Zhang Wei”. ORCID enables these names to be disambiguated
- CORE is currently developing an ORCID dashboard, which will enable repository managers to both to identify missing ORCID IDs,
- and to enrich your data with ORCID IDs found from elsewhere.
- prefix: |
- linkDocumentation: 0
- linkToolKit: https://orcid.org
- textToolKit: Link to documentation
- - id: ROR
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
+ - id: researchOutputs
isEnable: yes
type: statistic
- title: ROR
+ title: Do you provide information about funding bodies for the research outputs?
description: |
- recommendation: |
- The CORE Dashboard enables you to specify your ROR ID. You should check the details to make sure your institution is identified correctly.
- If the ROR ID is missing or incorrect, you can correct it on the dashboard. The ROR ID can be obtained from the [Research Organisation Registry](https://ror.org/) website.
- prefix: |
- - id: metadata
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
+ - id: informationAboutProject
+ isEnable: yes
+ type: statistic
+ title: Do you provide in the metadata information about project IDs?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
+ - id: metadataRecordsSupport
+ isEnable: yes
+ type: statistic
+ title: What proportion of your metadata records support deposit dates? (0-100%)
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
+ ########################################################################################################################
+ - id: fitFuture
isEnable: yes
type: text
- title: Metadata
+ title: Fit for future
description: |
- The repository ensures publications are accompanied by metadata to enable discovery, reuse, and citation,
- using schema that are appropriate to, and ideally widely used across, the communities that the repository serves.
- Metadata for the resource is recorded in a standard, interoperable, non-proprietary format. The repository
- assigns a CC0 public domain license to all metadata for resources in the repository.
- linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Metadata
- - id: signpostingFAIR
+ The first step in (re)using data is to find them. Metadata and data should be easy to find for both
+ humans and computers. Machine-readable metadata are essential for automatic discovery of
+ datasets and services, so this is an essential component of the FAIRification process.
+ - id: supportResourceSync
isEnable: yes
type: statistic
- title: FAIR Signposting
- description: |
- FAIR Signposting is a technical approach designed to enhance the discoverability and interoperability
- of scholarly resources on the web. It involves using standardized HTTP link relations to expose key information
- about web resources, particularly in the context of scholarly communication. This approach aligns with the broader
- FAIR principles, which aim for data to be Findable, Accessible, Interoperable, and Reusable.
- recommendation:
- FAIR signposting can be done adding information to HTTP headers.
- Specifically, the HTTP header can contain a element to describe the type of content resource, for example, “author”, or “collection”.
- linkDocumentation: 0
- linkToolKit: https://core.ac.uk/documentation/data-providers-guide#fair-signposting
- textToolKit: Link to documentation
- prefix: |
- - id: vocabulariesCOAR
+ title: Do you support ResourceSync
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
+ - id: COARNotify
isEnable: yes
type: statistic
- title: Use of COAR vocabularies
+ title: Do you support COAR Notify
description: |
- [COAR (Confederation of Open Access Repositories)](https://vocabularies.coar-repositories.org/) vocabularies are structured sets of terms organized to provide
- a common framework for the sharing and integration of data across different systems.
- They comprise three types: Access rights, resource types, and version types.
- recommendation: |
- A metadata profile such as RIOXX can provide an easy way to share and use COAR vocabularies in your metadata.
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an
+ application-independent interoperability framework based on metadata harvesting. Read more.
- - Access rights: describe the access status of a resource, such as “embargoed access”, or “restricted access”.
+ ########################################################################################################################
+ - id: environmental
+ isEnable: yes
+ type: text
+ title: Operational / Environmental considerations
+ description: |
+ We have run an automatic check of your repository. To get certification please arswer following questions:
- - Resource type: describe the type of resource, such as “patent”, “bibliography”, or “conference presentation”.
+ - id: isManageDeposits
+ isEnable: yes
+ type: statistic
+ title: How do you manage deposits? Is there someone to check them?
+ description: |
+ We serve the global network of repositories and journals increasing discoverability and preventing misuse of their content; making metadata records uniquely identifiable and resolvable with decentralised PIDs; supporting data providers in adopting good practices by providing tools for metadata validation, content management, enrichment and OA compliance; and facilitating machine access to open research.
- - Version type: distinguish the various states of an academic article, including the version of record (VOR), the Author’s Original (AO), and the Author’s Accepted Manuscript (AM).
- prefix: |
- - id: embargoedDocuments
+ - id: takeDownNotices
isEnable: yes
type: statistic
- title: Do you label embargoed documents?
+ title: How do you handle take-down notices
description: |
- Embargoed documents are articles that can only be made available open access after a stated interval, such as 90 days or six months.
- These delays are best managed when the embargo is tagged in a machine-readable way to ensure that machines can access and understand the policy.
- prefix: |
- Percentage of embargoed documents:
- recommendation: |
- There are various supported ways of tagging an embargo document, CORE recognises only a few of them.
- The [Rioxx specification](https://rioxx.net/profiles/v3-0-final/) recommend that they are tagged using “HTTP status 451 Unavailable For Legal Reasons”. https://rioxx.net/profiles/v3-0-final/
- If this number doesn't match the one in your records please review your system.
- - id: broadMeasuredReuse
+ We serve the global network of repositories and journals increasing discoverability and preventing misuse of their content; making metadata records uniquely identifiable and resolvable with decentralised PIDs; supporting data providers in adopting good practices by providing tools for metadata validation, content management, enrichment and OA compliance; and facilitating machine access to open research.
+
+ - id: preservationContentRepository
+ isEnable: yes
+ type: statistic
+ title: How do you manage the preservation of content in your repository?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ linkDocumentation: https://dashboard.core.ac.uk/
+ textLinkDoc: Answer the question
+
+ - id: preservationContentRepository
+ isEnable: yes
+ type: statistic
+ title: How do you encourage researchers to get their ORCID?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ linkDocumentation: https://dashboard.core.ac.uk/
+ textLinkDoc: Answer the question
+
+ - id: preservationContentRepository
+ isEnable: yes
+ type: statistic
+ title: What are you doing to promote FAIR principles?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ linkDocumentation: https://dashboard.core.ac.uk/
+ textLinkDoc: Answer the question
+
+ - id: preservationContentRepository
+ isEnable: yes
+ type: statistic
+ title: What are you doing to promote research reproducibility?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ linkDocumentation: https://dashboard.core.ac.uk/
+ textLinkDoc: Answer the question
+
+ - id: preservationContentRepository
isEnable: yes
+ type: statistic
+ title: How do you support Open Science at your institution?
+ description: |
+ The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. Read more.
+ linkDocumentation: https://dashboard.core.ac.uk/
+ textLinkDoc: Answer the question
+
+ ########################################################################################################################
+
+
+ - id: broadMeasuredReuse
+ isEnable: no
type: text
title: Broad and Measured Reuse
description: |
- The repository provides a landing page for each digital object that includes metadata required for citation of
- the object and provides this metadata in a machine-readable format. The repository collects and shares usage
- information using a standard protocol. The repository offers an API to facilitate machine action and bulk sharing.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Broad-and-Measured-Reuse
+ linkToolKit: 0
- id: statisticIRUS
- isEnable: yes
+ isEnable: no
type: statistic
title: Download statistic (IRUS)
description: |
- IRUS (Institutional Repository Usage Statistics) allows you to demonstrate the value and impact of your institutional
- repository (IR). It does this by enabling institutional repositories to share
- and compare usage statistics based on the COUNTER standard.
recommendation: |
- These statistics are available using the IRUS statistics aggregation service (IRUS-US for the USA, and IRUS-UK for the UK).
- By using a standard set of statistics, it becomes possible to provide meaningful stats to compare downloads across several repositories.
- IRUS uses the [COUNTER](https://www.countermetrics.org/) standard to measure usage statistics, such as “journal request”, or “book usage”.
- id: commonFormat
- isEnable: yes
+ isEnable: no
type: text
title: Common Format
description: |
- The repository allows resources and metadata to be accessed, downloaded, or exported from the repository in
- widely used, preferably non-proprietary, formats.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Common-Format
- - id: applicationProfile
- isEnable: yes
- type: statistic
- title: Your repository metadata supports a widely used Application Profile
- description: |
- Ensuring the usuage of a well-known application profile means that the metadata of the publication is described
- in a less ambiguous and more accurate way. Most used publications profiles are the OpenAIRE Guidelines 3.0+ and the
- RIOXX metadata application profile.
- prefix: |
- Your repository support RIOXXv2, RIOXXv3, OAIRE.
- recommendation: |
- CORE metadata indexing requires Dublin Core as a minimum; it supports OpenAIRE Guidelines; and it recommends RIOXX version 3.
- CORE recommends that repositories use [RIOXX v3](https://rioxx.net/profiles/), which we consider to be the most suitable metadata application profile for describing scholarly research outputs. Rioxx: The Research Outputs Metadata Schema was developed for institutional repositories to share metadata about the scholarly resources they contain.
- Information about how to comply with metadata recommendations are provided in the [CORE Data Provider’s Guide](https://core.ac.uk/documentation/data-providers-guide#meta-configuration).
+ linkToolKit: 0
- id: preservation
- isEnable: yes
+ isEnable: no
type: text
title: Preservation
description: |
- The repository has a plan in place to ensure the long-term management and preservation
- of publications and provides documentation of that plan. The management plan
- should include provisions for maintaining integrity, authenticity, and availability.
- The repository records basic preservation metadata including provenance, date of
- upload, and file format.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Preservation
+ linkToolKit: 0
- id: longTerm
- isEnable: yes
+ isEnable: no
type: text
title: Long-term Organizational Sustainability
description: |
- The repository has publicly available policies that outline the plan for its long-term management and funding,
- naming the organization responsible for its governance and continued management, and
- containing provisions for cessation of service. The host organization funds staff to support the repository and
- its users and publicly provides contact information for at least one individual charged with assisting users
- and the explicit responsibility of managing the repository services.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Long-term-Organizational-Sustainability
+ linkToolKit: 0
- id: curationQualityAssurance
- isEnable: yes
+ isEnable: no
type: text
title: Curation and Quality Assurance
description: |
- The repository provides or facilitates expert curation and quality assurance to improve the accuracy and
- integrity of digital objects and their metadata. This may include metadata enhancement, file integrity checks,
- and/or conversion to machine-readable formats. The repository provides documentation of what curation and quality
- assurance processes are applied to repository contents.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Toolkit
+ linkToolKit: 0
- id: provenance
- isEnable: yes
+ isEnable: no
type: text
title: Provenance
description: |
- The repository has mechanisms in place to record the origin, provenance, version control, and any other modifications to submitted digital objects and their associated metadata.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Provenance
+ linkToolKit: 0
- id: authentication
- isEnable: yes
+ isEnable: no
type: text
title: Authentication
description: |
- The repository supports authentication of its contributors. The repository has technical capabilities that facilitate associating contributor PIDs with those assigned to their deposited digital objects.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Authentication
+ linkToolKit: 0
- id: longTermTechnicalSustainability
- isEnable: yes
+ isEnable: no
type: text
title: Long-term Technical Sustainability
description: |
- The repository has a plan for long-term management and funding of its technical infrastructure.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Long-term-Technical-Sustainability
+ linkToolKit: 0
- id: securityIntegrity
- isEnable: yes
+ isEnable: no
type: text
title: Security and Integrity
description: |
- The repository has documented measures in place to meet well established cybersecurity criteria for
- preventing unauthorized access to or manipulation of its content and regularly monitors the integrity
- of its content. The repository has an emergency response plan in case of natural disaster, cyber attacks, etc.
linkDocumentation: 0
- linkToolKit: https://github.com/antleaf/USRN-Discovery/wiki/Security-and-Integrity
-usrnClosed: |
- DataProvider is not supporting FAIR
-usrnListDataProvider: [ ]
+ linkToolKit: 0
+ - id: freeAndEasy
+ isEnable: no
+ type: text
+ title: Free and Easy Discoverability & Access
+ description: |
+ linkDocumentation: 0
+ linkToolKit: 0
+ - id: clearUseGuidance
+ isEnable: no
+ type: text
+ title: Clear Use Guidance
+ description: |
+ linkDocumentation: 0
+ linkToolKit: 0
+ - id: licensingMetadata
+ isEnable: no
+ type: statistic
+ title: Licensing
+ description: |
+ prefix: |
+ recommendation: |
+ - id: uniquePersistentIdentifiers
+ isEnable: no
+ type: text
+ title: Unique Persistent Identifiers
+ description: |
+ linkDocumentation: 0
+ linkToolKit: 0
+ - id: researchDatasets
+ isEnable: no
+ type: statistic
+ title: Links to research datasets
+ description: |
+ prefix: |
+ - id: doi
+ isEnable: no
+ type: statistic
+ title: DOI
+ description: |
+ prefix: |
+ - id: ORCID
+ isEnable: no
+ type: statistic
+ title: ORCID
+ description: |
+ prefix: |
+ linkDocumentation: 0
+ linkToolKit: 0
+ textToolKit: Link to documentation
+ - id: ROR
+ isEnable: no
+ type: statistic
+ title: ROR
+ description: |
+ recommendation: |
+ prefix: |
+ - id: metadata
+ isEnable: no
+ type: text
+ title: Metadata
+ description: |
+ linkDocumentation: 0
+ linkToolKit: 0
![{textsFAIR.certificates.typeCertificates[key].title}]({)
+