-
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
Please add type property to RIF-CS licence element #48
Comments
Hi Grant, I agree that we should look to get this into the default distro - I'd like to update our RIF once v1.5 is officially released. Looking at a sample RIF segment: We do identify the licence URL so could provide that attribute and could deduce the type from the label or the URL.
I'll shy away from providing a fix here but it looks achievable based on what's there. Cheers, Duncan |
Here is a hack (excerpt) for Creative Commons licence types in home/templates/rif.vm
|
A similar principle applies to RIF-CS accessRights-type of Open, Conditional and Restricted (see http://guides.ands.org.au/rda-cpg/rights#accessRights) Eg. If we specify a type such as that below, RDA will show an Open logo.
Below is a hack (excerpt) for Creative Commons licence types and accessRights types in home/templates/rif.vm which supersedes the above version (with a shorter regular-expression match and replace). [It is a hack because it would be better if types were defined much earlier in the submission forms.]
|
I would like to recommend that RIF-CS rights/licence element be updated to include the "type" property as per http://www.ands.org.au/guides/cpguide/cpgrights.html#licence and http://www.ands.org.au/guides/cpguide/cpgrights.html#examples . Eg.
Without the type property, RDA shows "Unknown" at the top of the licence section (in the right pane). With the type property set, RDA will show text or a logo representing the licence type.
It would be preferred if this change was applied to all workflows where licence can be selected (which I suspect currently is only the main dataset workflow).
Thank you.
The text was updated successfully, but these errors were encountered: