-
Notifications
You must be signed in to change notification settings - Fork 10
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
Adding CC licenses to ERA theses #3142
Comments
Looking at prior work in Jupiter, Items already have a controlled vocabulary for the license. We can probably re-use the pattern we have for Jupiter Items to have either a rights statement or licence uri. We don't know what licence or licenses FGSR will choose but can probably adapt. Obviously, one controlled vocabulary is easier and more elegant than using many. Our system maps the URI to human-readable text. Here are the two parts: jupiter/config/controlled_vocabularies/era/license.i18n.yml Lines 1 to 9 in f531859
Lines 905 to 915 in f531859
You can see some of the patterns for rights/license here: Line 31 in f531859
Line 45 in f531859
Line 377 in f531859
jupiter/app/views/items/_item.html.erb Lines 75 to 85 in f531859
|
Does this have any impact on DSpace migration or planning? Is there feature parity there? |
Google ScholarMeta tagsEdit |
The text was updated successfully, but these errors were encountered: