Skip to content
Configuring the metadata of your FDP
The FAIR Data Point uses a lot of fields to describe detailed metadata of the applications, users and corresponding datasets that you are servicing with the FDP. In order to allow all FDPs to be integrated in the Humanitarian Data Space and in the African Health Data Space, it is important that these fields are filled in uniformly. Here we describe how to edit the FDP to meet the requirements, and then describe how to fill in the metadata fields in each layer.
Instructions on metadata in the FDP
1. FAIR Data Point = Top-Level/Entry Point
Controlled by one organization/group/person
FAIR Data Point = Top-Level/Entry Point
Metadata modified
Lasted edited on date
Metadata issued
Date created (automatic)
Metadata identifier
Automated – don’t touch
UI Language
Leave empty
End date
Leave empty
Start date
Leave empty
Contact point
Email address of administrator of the FDP
Include mailto: to make this interactive/clickable, e.g.:
mailto:mailme@example.com
Has policy
Leave empty
Rights
Leave empty
License
Leave as is (https://opensource.org/license/MIT)
Language
The language used for the descriptions in the FDP. English:
Other languages, find the proper URI on:
Version
Version of this FDP page. Format = A.B starting with 1.0
Minor changes bring up B by 1 (e.g. 1.2 -> 1.3)
Major changes bring up A by 1 and set B to 0 (e.g. 1.3 -> 2.0)
Publisher
Name (or URI) of the person or organization that is responsible for the FDP
Description
Extensive description of the entire FDP as a whole
Title
Name of the organization + FAIR Data Point. E.g. EEPA FAIR Data Point or Tangaza University FAIR Data Point
Endpoint description
Leave empty
There are no rows in this table
2. Catalog Level = Application Level
Each catalog is an application (containing hetereogeneous data)
Catalog Level = Application Level
Home page
URL to the GitHub repository of the application code
Common data model
Link to the application CDM on GitHub or BioPortal.
If this doesn’t exist yet, make it same as Home Page.
Contact point
Email address of administrator of this instance of the application
Include mailto: to make this interactive/clickable, e.g.:
mailto:mailme@example.com
Has policy
Leave empty
Rights
Leave empty
License
Leave as is (https://opensource.org/license/MIT)
Language
The language used for the descriptions in the FDP. English:
Other languages, find the proper URI on:
Version
Version of this FDP page. Format = A.B starting with 1.0
Minor changes bring up B by 1 (e.g. 1.2 -> 1.3)
Major changes bring up A by 1 and set B to 0 (e.g. 1.3 -> 2.0)
Publisher
Name (or URI) of the person or organization that is responsible for this part of the FDP.
Description
Extensive description of the application and how it is being deployed/used in this context.
Title
Name of the application – this is standardized, look at the examples and make sure it is the same.
There are no rows in this table
3. Dataset Level = User Level
Each user (person/organization) using the application. All data in a dataset is homogeneous
Dataset Level = User Level
Landing Page
Leave empty
Keyword
Fill in one or more keywords as words that represent the type of data collected by this user in this application.
Theme
Fill in the URIs of themes related to the data collected by this user in this application. Look at the examples on EEPA or Tangaza FDPs for inspiration.
Modified
Lasted edited on date
Issued
Date created (automatic)
Common data model
Link to the application CDM on GitHub or BioPortal.
If this doesn’t exist yet, make it the application code on GH.
Contact point
Email address of person responsible for the data
Include mailto: to make this interactive/clickable, e.g.:
mailto:mailme@example.com
Has policy
Leave empty
Rights
Leave empty
License
Leave as is (https://opensource.org/license/MIT)
Language
The language used for the descriptions in the FDP. English:
Other languages, find the proper URI on:
Version
Version of this FDP page. Format = A.B starting with 1.0
Minor changes bring up B by 1 (e.g. 1.2 -> 1.3)
Major changes bring up A by 1 and set B to 0 (e.g. 1.3 -> 2.0)
Publisher
Name (or URI) of the person or organization that is responsible for this part of the FDP.
Description
Description of this user of the application, created in agreement with that user.
Title
Name of the user of this application in your context
There are no rows in this table
4. Distribution Level = Data Level
Each user (person/organization) using the application. All data in a dataset is homogeneous
Distribution Level = Data Level
Byte size
Leave empty
Format
If a repository included for Access URL, paste:
Media Type
If a repository included for Access URL, paste:
Download URL
Leave empty
Access URL
If there is a connected repository give the URL of that repo without ‘/sparql’ at the end, e.g.:
Modified
Lasted edited on date
Issued
Date created (automatic)
Common data model
Link to the application CDM on GitHub or BioPortal.
If this doesn’t exist yet, make it the application code on GH.
Contact point
Email address of person responsible for the data
Include mailto: to make this interactive/clickable, e.g.:
mailto:mailme@example.com
Has policy
Leave empty
Rights
Leave empty
License
Leave as is (https://opensource.org/license/MIT)
Language
The language used for the descriptions in the FDP. English:
Other languages, find the proper URI on:
Version
Version of this FDP page. Format = A.B starting with 1.0
Minor changes bring up B by 1 (e.g. 1.2 -> 1.3)
Major changes bring up A by 1 and set B to 0 (e.g. 1.3 -> 2.0)
Publisher
Name (or URI) of the person or organization that is responsible for this part of the FDP.
Description
Description of this dataset, what it represents and its use.
Title
Name of the sub-dataset
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.