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

Feature/pid model improvements #25

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

markdoerr
Copy link

  • some suggestions (as discussed) for the improvements of the terms (making them clearer)
  • removing obsolete fields in the handle record schema
  • fixing some typos

@@ -141,9 +142,10 @@ slots:
multivalued: true
description: Relations of the resource to other identifiers
dc_rights:
# TODO: why not call it just license(s) ?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Please change directly to license.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rename file to "README.md"

@@ -60,6 +60,7 @@ classes:
PID4CatRelation:
description: >-
A relation between PID4CatRecords or between a PID4CatRecord and other resources with a PID.
# TODO: please provide and example for this class
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove. General todos should better be issues. There is already #24 for this.

slot_uri: schema:email
description: Identification of the agent that registered the PID, with
contact information. Should include person name and affiliation, or position
name and affiliation, or just organization name. e-mail address is preferred
contact information.
person_orcid:
TODO: should be better defined - to be clearly parsable by machines
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! This should also have the email-regex as above for curation_contact pattern: "^\\S+@[\\S+\\.]+\\S+"
Feel free to add it already now.

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

Successfully merging this pull request may close these issues.

2 participants