uoregon-libraries / oregon-oni

Oregon theme / customizations for use with Open ONI
1 stars 0 forks source link

Where are the copyright statements? #67

Open sseymore opened 3 years ago

sseymore commented 3 years ago

The copyright statements for each title are not visible from the front-end/public view. Was this lost in the migration? Needs investigation.

jechols commented 3 years ago

Sorry for the delay, I'm looking into this right now as I try to clear some of my "quick" backlogged to-do items.

It looks like the problem here is entirely on my end, and indeed during the migration. I'm not sure how I missed this stuff, but the copyright data is no longer in the database at all.

I can use NCA's information to determine which titles need data presented, but there's a small problem: for each copyright URI, I need some accompanying text to display. e.g., we'd probably want "Public Domain" for the URI http://creativecommons.org/publicdomain/mark/1.0/.

Here's all the rights URIs we have, and my best guess at the text based on what the URLs point to:

If you can get me the proper text for those, I can get things moving when I have some time.

sseymore commented 3 years ago

These look great, but I have one question. Will there also be a rolling public domain override for any formerly-licensed content? For instance, if a current publisher allows digitization of 1926 issues with a CC license, will that license update to public domain in 2022? I hope this makes sense.

From: Jeremy Echols notifications@github.com Reply-To: uoregon-libraries/oregon-oni reply@reply.github.com Date: Monday, January 4, 2021 at 9:57 AM To: uoregon-libraries/oregon-oni oregon-oni@noreply.github.com Cc: Sarah Seymore sseymore@uoregon.edu, Author author@noreply.github.com Subject: Re: [uoregon-libraries/oregon-oni] Where are the copyright statements? (#67)

Sorry for the delay, I'm looking into this right now as I try to clear some of my "quick" backlogged to-do items.

It looks like the problem here is entirely on my end, and indeed during the migration. I'm not sure how I missed this stuff, but the copyright data is no longer in the database at all.

I can use NCA's information to determine which titles need data presented, but there's a small problem: for each copyright URI, I need some accompanying text to display. e.g., we'd probably want "Public Domain" for the URI http://creativecommons.org/publicdomain/mark/1.0/https://urldefense.com/v3/__http:/creativecommons.org/publicdomain/mark/1.0/__;!!C5qS4YX3!UM2GQRXwU_GHrl8gAvgf5UmZNh4hsZ61m79nGJRqlO6q3vd193giqQAHeNp3EU1c7w$.

Here's all the rights URIs we have, and my best guess at the text based on what the URLs point to:

If you can get me the proper text for those, I can get things moving when I have some time.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/uoregon-libraries/oregon-oni/issues/67*issuecomment-754122799__;Iw!!C5qS4YX3!UM2GQRXwU_GHrl8gAvgf5UmZNh4hsZ61m79nGJRqlO6q3vd193giqQAHeNo16ZL2cQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABX5IBWMSDS6IQ4YJOFYSY3SYH6RJANCNFSM4RNMBLTQ__;!!C5qS4YX3!UM2GQRXwU_GHrl8gAvgf5UmZNh4hsZ61m79nGJRqlO6q3vd193giqQAHeNoFpxi79A$.

jechols commented 3 years ago

The system in ONI can use a date range, but everything prior to 1923 gets forcibly set to being Public Domain so long as that URI is in our database (it currently isn't) . So we'd probably set everything to be a given rights statement from 1923 until basically 9999 or something crazy so it acts as a "forever" date. I think that's what you want, but let me know if not.

sseymore commented 3 years ago

I'm not sure I understand. The public domain is now "rolling" every year, so it would be great to add public domain to all issues through the end of 1925 (as of 2021). Then, in 2022, all of the 1926 issues would also enter the PD and get that statement. I realize that's more work-- might just need another ticket for now?

jechols commented 3 years ago

Sorry for the delay, I saw this and then got sidetracked again on other fires.

I was not aware of the rolling PD date. That definitely complicates things a little, but I think I could submit a change to ONI to handling this logic. It seem like it would be simple enough - if current year minus issue publication year is 96 or greater, it's magically PD regardless of the database rules. Does that seem correct? I'll look into this today.

sseymore commented 3 years ago

Yes, it seems like that approach should work.

From: Jeremy Echols notifications@github.com Reply-To: uoregon-libraries/oregon-oni reply@reply.github.com Date: Thursday, January 28, 2021 at 8:38 AM To: uoregon-libraries/oregon-oni oregon-oni@noreply.github.com Cc: Sarah Seymore sseymore@uoregon.edu, Author author@noreply.github.com Subject: Re: [uoregon-libraries/oregon-oni] Where are the copyright statements? (#67)

Sorry for the delay, I saw this and then got sidetracked again on other fires.

I was not aware of the rolling PD date. That definitely complicates things a little, but I think I could submit a change to ONI to handling this logic. It seem like it would be simple enough - if current year minus issue publication year is 96 or greater, it's magically PD regardless of the database rules. Does that seem correct? I'll look into this today.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/uoregon-libraries/oregon-oni/issues/67*issuecomment-769212220__;Iw!!C5qS4YX3!RLUPqX6EE-yDRJz-CtDHrcEq0b26OGcI3JIx_IBHuCwYV3V3EISsWssEpsfkJsiuQQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ABX5IBS4ZTAHE2N6N6SJYW3S4GHHZANCNFSM4RNMBLTQ__;!!C5qS4YX3!RLUPqX6EE-yDRJz-CtDHrcEq0b26OGcI3JIx_IBHuCwYV3V3EISsWssEpscrXUpQlQ$.

jechols commented 3 years ago

The rolling PD (and PD info in general) is fixed via https://github.com/open-oni/open-oni/pull/576, so once that's in ONI and we have another ONI release, we'll be set. Then I can get our title-specific copyright stuff into our local ONI.