-
Notifications
You must be signed in to change notification settings - Fork 1
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
Modify DOI Abstract
to facilitate better abstracts being submitted
#992
Comments
Related card 915 |
After discussing this with @bhonick it might be useful to break out abstract into 3 distinct fields:
This would give end users a clear a defined structure for what we expect as an abstract and having this broken out into components would allow for better mining of the abstracts. When publishing a dataset we would simply concatenate these fields to create the abstract in the DOI. For registration purposes we would make these fields required but not put a character requirement to create a dataset. We would show a warning symbol (similar to how we handle protocol DOIs) if the field is below a certain character threshold (100 characters). We would then add a check prior to processing the dataset that all of these fields meet the character threshold. This allows data providers to quickly register datasets but forces them to enter detailed information well before publishing them. We would also need to update the bulk registration process to:
|
We will need to change the existing |
Can potentially link out to this as an example abstract: https://www.nlm.nih.gov/bsd/policy/structured_abstracts.html Can utilize these points in the popover: https://www.nature.com/documents/nature-summary-paragraph.pdf
|
Abstract
or something more descriptivePotentially
We could break out this one field into multiple components then splice it together in the dataset view to create a single abstract description
We could either make this a required field
We could place a word minimum on this field
The text was updated successfully, but these errors were encountered: