-
Notifications
You must be signed in to change notification settings - Fork 6
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
Proposal to import dc:publisher #173
Comments
An analogous situation involving images might be images submitted to iNaturalist where the submitter is an individual with no web presence and iNaturalist is likely to be the only place where the images would be maintained for access. |
We publish a lot of third-party images for the first time in our flora products as well. We should have a think – and add some notes – about the difference between this and |
To take a couple of real examples from bio.acousti.ca: In the first we have copies of recordings that were originally published alongside a book on the publisher's website. In this case that publisher is dc:publisher and bio.acousti.ca is ac:provider? In the second bio.acousti.ca has recordings of mine that I have not otherwise published. In this case bio.acousti.ca is both dc:publisher and dc:provider? |
At the Maintenence Group meeting on 22/08/2024 it was decided to work through this and related issues by developing some 'recipes for using rights' in the document here: https://docs.google.com/document/d/1Nv0rNWioJIX-DJRxQExmd22BmaU48qdRYQSzRzdyMQU/edit?usp=sharing. Please feel free to add usage examples to the document for review at the next meeting. |
To give a sound based example, BioAcosutica include recordings made by an individual who is the legal owner, but BioAcoustica is the primary source by which that recording is made available to the public. In this case dc:publisher seems to be something worth adding explicitly to AudubonCore.
The text was updated successfully, but these errors were encountered: