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

Entry ownership and editing rights (preservation of) #3

Open
joncison opened this issue Feb 1, 2019 · 3 comments
Open

Entry ownership and editing rights (preservation of) #3

joncison opened this issue Feb 1, 2019 · 3 comments

Comments

@joncison
Copy link
Contributor

joncison commented Feb 1, 2019

One of many issues around GitHub-based content management for bio.tools.

@joncison
Copy link
Contributor Author

joncison commented Feb 1, 2019

Should we preserve the existing ownership and editing rights model, extend it, or abandon it?

  • rights should be preserved if an individual or institute want this (there are current examples)
  • existing entry ownership / edit-rights would have to be annotated (on entry level) as GitHub handles
  • meaning some mechanism to map bio.tools accounts to GitHub accounts would be needed

@joncison joncison changed the title Entry ownership and editing rights (preservation of?) Entry ownership and editing rights (preservation of) Feb 1, 2019
@osallou
Copy link
Collaborator

osallou commented Mar 15, 2019

contributors could appear in a dedicated field to keep history of who contributed and when, but would not prevent editing

@joncison
Copy link
Contributor Author

We'd need, I think, to tweak the existing "credit" model :
https://biotoolsschema.readthedocs.io/en/latest/biotoolsschema_elements.html#credits-group

credit->typeEntity would be "Person" and credit->typeRole would be "Documentor"

We'd need to add githubid (GitHub User ID) - similar to the orcidid that's already there

And something for the date (when entry was edited) - but I'm not sure where / how to model it exactly. Could add a field to credit, but it needs some thought (could be a better way?)

cc @hansioan @piotrgithub1 @matuskalas @bgruening

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