| Metadata component . | FAIR Guidelines . | Question for the domain community participating in the M4M workshop . | Metadata . | Implementation considerations . | Kampala International University Uganda FDP 1.1 . |
|---|---|---|---|---|---|
| 1 | F1 | What is the persistence policy for the identifier systems used for digital assets? | Policy statement from the domain community regarding the requirements for identifier systems | Unless the domain community builds its own identifier services, a widely reused policy will simply default to the policy of existing services (such as DOIs or PURLs) that may be chosen based on a range of other considerations. | PURL/hospital persistent URL |
| 2 | F2 | What is the minimum acceptable profile needed to ensure findability? | Examples: people, institutions, geographical locations, date/time, funding source, publishers, repositories | The schema for many of these metadata elements are often highly generic and reusable. | Geographical locations, institutions, date/time, repositories, publisher |
| 3 | F4 | What are the minimum acceptable indexing requirements and limitations? | Metadata that comply with indexers and search algorithms | Exceptions for established repositories and domain communities will likely rely on commercial indexing and search such as Google and Bing. Rich and semantically enabled metadata search solutions are emerging in third parties/companies. | |
| 4 | A1.1 | What access policies and protocols are in place for this community? | Self-describing access restrictions, based on policy | Existing authentication and authorisation technologies will likely be reused, coupled with ontologically enabled access conditions. | Hospital patient data is only accessed by the hospital data management personnel. |
| 5 | A2 | What is the persistence policy for the metadata? | Policy statement from the domain community regarding the requirements for metadata longevity | A metadata standard for this element does not yet exist, but version 1.0 can be easily created referencing the policy document and widely reused. | In Uganda, archiving metadata to be saved permanently is done. |
| 6 | I2 | How FAIR are the vocabularies? | Metadata linking to canonical descriptions of terminology systems, vocabularies and ontologies | The FAIRness of these resources can be measured using FAIR evaluation tools and these evaluations could also be reported as metadata. | Open Science Framework |
| 7 | R1.1 | What usage licence(s) will be used? | Metadata linking to machine-actionable licence | See, for example, the licences available in the Open Science Framework. | CC Licence |
| 8 | R1.2 | What are the minimum provenance metadata needed to ensure reuse? | Examples: laboratory methods, analytical methods, computational platforms | The schema for these metadata elements are often highly specific and idiosyncratic to the use case. In general, these elements will require the most time and resources to develop. | |
| 9 | R1.3 | What FAIR Implementation Profile (FIP) is used to make data/metadata FAIR? | A machine-actionable list of the FAIR-enabling resources used to make the data and metadata FAIR | Example: VODAN FIP | VODAN FIP |
| Metadata component . | FAIR Guidelines . | Question for the domain community participating in the M4M workshop . | Metadata . | Implementation considerations . | Kampala International University Uganda FDP 1.1 . |
|---|---|---|---|---|---|
| 1 | F1 | What is the persistence policy for the identifier systems used for digital assets? | Policy statement from the domain community regarding the requirements for identifier systems | Unless the domain community builds its own identifier services, a widely reused policy will simply default to the policy of existing services (such as DOIs or PURLs) that may be chosen based on a range of other considerations. | PURL/hospital persistent URL |
| 2 | F2 | What is the minimum acceptable profile needed to ensure findability? | Examples: people, institutions, geographical locations, date/time, funding source, publishers, repositories | The schema for many of these metadata elements are often highly generic and reusable. | Geographical locations, institutions, date/time, repositories, publisher |
| 3 | F4 | What are the minimum acceptable indexing requirements and limitations? | Metadata that comply with indexers and search algorithms | Exceptions for established repositories and domain communities will likely rely on commercial indexing and search such as Google and Bing. Rich and semantically enabled metadata search solutions are emerging in third parties/companies. | |
| 4 | A1.1 | What access policies and protocols are in place for this community? | Self-describing access restrictions, based on policy | Existing authentication and authorisation technologies will likely be reused, coupled with ontologically enabled access conditions. | Hospital patient data is only accessed by the hospital data management personnel. |
| 5 | A2 | What is the persistence policy for the metadata? | Policy statement from the domain community regarding the requirements for metadata longevity | A metadata standard for this element does not yet exist, but version 1.0 can be easily created referencing the policy document and widely reused. | In Uganda, archiving metadata to be saved permanently is done. |
| 6 | I2 | How FAIR are the vocabularies? | Metadata linking to canonical descriptions of terminology systems, vocabularies and ontologies | The FAIRness of these resources can be measured using FAIR evaluation tools and these evaluations could also be reported as metadata. | Open Science Framework |
| 7 | R1.1 | What usage licence(s) will be used? | Metadata linking to machine-actionable licence | See, for example, the licences available in the Open Science Framework. | CC Licence |
| 8 | R1.2 | What are the minimum provenance metadata needed to ensure reuse? | Examples: laboratory methods, analytical methods, computational platforms | The schema for these metadata elements are often highly specific and idiosyncratic to the use case. In general, these elements will require the most time and resources to develop. | |
| 9 | R1.3 | What FAIR Implementation Profile (FIP) is used to make data/metadata FAIR? | A machine-actionable list of the FAIR-enabling resources used to make the data and metadata FAIR | Example: VODAN FIP | VODAN FIP |