Adding CC licenses to ERA theses

pgwillia commented 1 year ago

I am writing this email to notify you of good progress made on efforts by our Copyright Office to challenge FGSR to enable graduate students to choose a CC license for their ETDs. The current state is nearly an 'all rights reserved' state, except for the Library permission, so a desired state where students can set terms of use is a big step forward for these open and amazing representations of scholarly work. FGSR is highly supportive and has asked us all who work with ETDs to proceed with implementation 🎉

There will be implications for us. 1) The AlFresco form will change and the students will be presented with:

a) Do you want to choose a CC license? yes/no

b) Selection of CC license based on usability (radio button or drop down, whatever Suresh's team feels makes the most sense).

Suresh Joshee asked me if there is a controlled vocabulary code that our team would recommend for CC license choices. I presume there is one, and we are already using it, but we should provide documentation/a pointer for him to be good organizational citizens.

2) We will have to decide how to structure this new data in Jupiter inside the data model and how to depict it in the interface. I know we will have several choices and should discuss those together. We may want to choose the LEAST impactful option, even if it is not ideal, depending on how complicated this seems to the various teams involved.

I will call a meeting to discuss. Please tell me who should come to this meeting.

3) The implementation date for this is tentatively October 2, 2023. This is an FYI for you as you think about any work that needs to be scoped and deployments that would be necessary.

I will wait to hear from you on the answer to #2 above and will call a meeting. This is an exciting development! But it does involve effort and thought, and has work and time implications we definitely need to discuss.

pgwillia commented 1 year ago

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: https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/config/controlled_vocabularies/era/license.i18n.yml#L1-L9

https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/config/locales/en.yml#L905-L915

You can see some of the patterns for rights/license here: https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/app/models/item.rb#L31 https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/app/models/item.rb#L45 https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/db/schema.rb#L377 https://github.com/ualbertalib/jupiter/blob/f5318597c07934834c651438a59db46da36ec35d/app/views/items/_item.html.erb#L75-L85

pgwillia commented 1 year ago

Does this have any impact on DSpace migration or planning? Is there feature parity there?

pgwillia commented 1 year ago

thesis_cc.pdf