Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define SoilWise metadata profile #1

Open
1 task done
DajanaSnopkova opened this issue May 3, 2024 · 3 comments
Open
1 task done

Define SoilWise metadata profile #1

DajanaSnopkova opened this issue May 3, 2024 · 3 comments
Assignees

Comments

@DajanaSnopkova
Copy link

DajanaSnopkova commented May 3, 2024

Definition of metadata profile, that will be used for core validation, that will be applied to all harvested metadata resources. A combination of INSPIRE and DublinCore is under consideration.

  • Find out what was used for EJPSoil

Links to Prepare ETS config for core metadata validation, it needs to be agreed, for what purpose the results of this core validation will be used (e.g. displaying and findability of the metadata resource, ranking in search results...)

@pvgenuchten
Copy link
Contributor

see also:

issue 3 above has the ejpsoil profile extended with some new issues

@pvgenuchten pvgenuchten self-assigned this Jun 6, 2024
@DajanaSnopkova
Copy link
Author

SoilWise metadata profile is defined as EJPSoil metadata profile extended by few record as defined by the ESDAC WG in the following Excel.
EUSO Data WG metadata template-final-proposal (2).xlsx

@pvgenuchten
Copy link
Contributor

Note that EJPSoil is much too extended to act as core model (notice that #16 states that records which do not validate the core profile, are rejected from the catalogue), suggestion for minimal is:

  • identifier
  • title
  • date
  • contact point
  • source catalogue

what do you think @DajanaSnopkova

@pvgenuchten pvgenuchten reopened this Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants