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

Add remark field to metadata #73

Closed
pjotrp opened this issue May 30, 2020 · 5 comments
Closed

Add remark field to metadata #73

pjotrp opened this issue May 30, 2020 · 5 comments
Assignees
Milestone

Comments

@pjotrp
Copy link
Collaborator

pjotrp commented May 30, 2020

A random remark field is probably a good idea. It can lead to additions to the schema. Also I think we can allow for additional RDF if people want that. At least give a proposal field.

@LLTommy
Copy link
Collaborator

LLTommy commented Jun 8, 2020

Have a look at the example yaml here. Almost all sections do have a "additional_**_information_field" which is meant as a free text field to comment (as defined in SIO http://semanticscience.org/resource/SIO_001167). Does this answer your question?

@pjotrp
Copy link
Collaborator Author

pjotrp commented Jun 12, 2020

Does this answer your question?

Partly. One free text field for the whole form would be great. I am also thinking of allowing the injection of RDF, however. Maybe this is evil, but it would allow for a lot of freedom in adding metadata. Question is how you keep track of it ;)

@pjotrp pjotrp added this to the v1.2 milestone Jun 12, 2020
@LLTommy
Copy link
Collaborator

LLTommy commented Jun 12, 2020

Maybe I accept an additional comment file for the whole thing. However, I really don't know what additional metadata you want, especially if we include #77? You'd be lucky if you have all this metadata to go along with a submission, don't you think so? I'd say, let's try to keep up with what we have planned so far ... for now we have enough to address.

@pjotrp
Copy link
Collaborator Author

pjotrp commented Jun 13, 2020

If someone wants to add a field for eye color they could do that immediately. We can follow with pyshex after if we think it is worth the trouble. It is that type of flexibility for end users. But then it may be better we just handle it ourselves (to avoid SPAM, for one).

@pjotrp pjotrp self-assigned this Jun 13, 2020
@pjotrp
Copy link
Collaborator Author

pjotrp commented Oct 29, 2020

Can be done when someone has a use case.

@pjotrp pjotrp closed this as completed Oct 29, 2020
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

2 participants