Comments (6)
Please add:
pbcoreRightsSummary_rightsSummary: Copyright Status (Public Domain - Copyrighted - Copyright status unknown) -- Required
pbcoreRightsSummary_rightsSummary: Copyright Statement (see boilerplate © statements) -- Required
pbcoreRightsSummary_rightsSummary: Copyright Holder -- Preferred
pbcoreRightsSummary_rightsSummary: Copyright Holder Info -- Preferred
pbcoreRightsSummary_rightsSummary: Copyright Date -- Preferred
pbcoreRightsSummary_rightsSummary Copyright Notice -- Ideal
pbcoreRightsSummary_rightsLink: URI if supplied by Library/Archive -- Ideal
from collengine.
These were the fields we had before
https://github.com/tingletech/collengine/blob/master/items/models.py#L197
how to handle the boilerplate is what has me stuck; but I was just going to put in fields for what it commented out in the models.py...
from collengine.
hi Brian,
I updated the field names so they relate to each instantiation (per pbcore v.2) and I liked the idea of a rights link. Can we change the fields in the model? I took copyright holder info out because this might be private information, and I don't see a point to holding onto non-public information when the current system exports all fields.
thank you
pamela
from collengine.
The names you use are not valid names (/'s and spaces) with respect to the models.py...
Why do you want to keep private information about rightsholders? Shouldn't you record who they are (but not phone # social etc.) and contact info for who to contact to clear further rights (which might be the phone of the rightsholder)
I have not looked at the new PBCore yet but tracking rights at the instantiation level seems like a major change -- right now in here it is at the leve of the work as a whole.
For this project and workflow, do you anticipate different rights for the different files?
Are there extant "rights links"?
While we don't use the schema at this URL, this is a source I take as authoritative as far as what rights information we want to collect and display in OAC/Calisphere so that end users can make an informed decision about further use of materials discovered on our site. http://www.cdlib.org/groups/rmg/ Adrian has an interpretation of this as a set of rights fields that is used for LHDRP project and I think we should try to stick to Adrian's fields if possible.
from collengine.
- can you use an underscore rather than a / for models names?
- we're recording the name of the rights holder but not their contact information. If someone wants to contact the rights holder to clear further rights, I think it's fine if they go through the institution. Originally I included Owner contact information, but I think for some items there might be privacy issues. Is there a way to repress this info so it doesn't export?
- I think rights information will be the same for the asset on an item level and on each file level. But I'd like to allow these fields either here or in another db like Collection Space, in case rights change.
- No rights links yet, we'll see if participants can supply them!
- I'm following LHDRP's (c) standards - all fields except for Copyright Holder Info
from collengine.
At this time, let's stick to Rights on an Asset-level (forget my rights per Instantiation idea). I'll save that idea for another day.
from collengine.
Related Issues (20)
- Please delete Definition_Choices field HOT 2
- Please create pbcoreAssetType field HOT 6
- please delete Mix_Type_Choices HOT 1
- Change "runningSpeed" field name to essenceTrackFrameRate; add essenceTrackPlaybackSpeed field HOT 6
- add instantiationEssenceTrack_essenceTrackPlaybackSpeed field HOT 1
- Below Collection field can we add "pbcoreCollection" field to contain URL for finding aid? HOT 2
- Please delete carrier ID field
- Please add instantiationEssenceTrack_essenceTrackType as a required field HOT 2
- I would like you to change the "inscription" field name to objectTitle. HOT 1
- Please change DateIssued field name to DatePublished
- Please add Temporal Coverage field after Date Created and Date Published fields
- Please add SpatialCoverage Field after SubjectPlace field
- Please add GeospatialCoverage Field after SpatialCoverage Field
- Please change contributorPublisher field name to Publisher field
- Please change Physical Format field name to "instantiationPhysical"
- Please add field "instantionDimensions" after "instantiationPhysical"
- please change "formatDuration" field name to "instantiationDuration" and please add instantiationTimeStart field after formatDuration field
- please add "instantiationAlternativeModes" field after encoding choices
- please add "essenceTrackAspectRatio" field after instantiationDimensions field
- please add "Relation" and "RelationType" fields after genreForm field
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from collengine.