-
Notifications
You must be signed in to change notification settings - Fork 9
Consider combining creatorRole, contributorRole, and publisherRole vocabs #93
Comments
Hi Casey - This has been mentioned already in #87 The Vocab team discussed this issue the other day, and we are very likely going to combine Creator and Contributor Role into a single list. But, I'm inclined to think that other agent roles (publisher, distributor, copyright holder, etc.) should probably be maintained in a separate list. Creators and contributors are agents directly responsible for the creation of the intellectual or artistic content of the work. For this reason, I think that other agent-type roles, which do not contribute to the creation of the work, should be maintained in a separate list, so as not to cause confusion for potential users as to which elements they should use to link these people. But, I'm open to other thoughts about it. |
Hi Ann, I still feel strongly that one role code would suffice. EBUCore includes a role of "Copyright Holder" in its role code, as well as "Copyright Agent." One section of EBU's Role Code is "Distribution," which includes terms such as Distribution Company, Distributor, Publishing Company, Publisher, Disseminator, Release Agent, etc. From: AllisonAnn <[email protected]mailto:[email protected]> Hi Casey - This has been mentioned already in #87#87 The Vocab team discussed this issue the other day, and we are very likely going to combine Creator and Contributor Role into a single list. But, I'm inclined to think that other agent roles (publisher, distributor, copyright holder, etc.) should probably be maintained in a separate list. Creators and contributors are agents directly responsible for the creation of the intellectual or artistic content of the work. For this reason, I think that other agent-type roles, which do not contribute to the creation of the work, should be maintained in a separate list, so as not to cause confusion for potential users as to which elements they should use to link these people. But, I'm open to other thoughts about it. — |
I also like the EBU role list very much. Maybe we shouldn't have a pbcore Role list at all, and just recommend the EBU list. I think maybe the issue is not so much having all Roles in a single list as it is a documentation issue in defining the elements, including how the Publisher element is to be expanded (or not) to include Distributors and other types of third party agents. I think that the documentation should be very clear to people what Creator, Contributor, and Publisher means. Then, assigning the correct role types to the names in these elements, should be less problematic for users. |
I did a lot of work on the MARC relator (role) list, including reconciling it with the RDA role list (and back in 2004/2005 how the roles are used with Dublin Core). I think it is too constraining to separate creators and contributors, since it often depends on the context which you consider a given agent. And in general coming up with rules for which roles contribute to intellectual content is difficult. It is true that publishers and distributors don't contribute to intellectual content, but I'm not sure what the value is of separating them and requiring separate role lists. I agree that it can be handled with documentation. |
Hi all! Have any decisions been made as to what is happening with the pbcore Role elements and whether or not we should refer to the EBU role list it? Is the Role list being parsed down to one role/element? And if so, what is it going to be called? Thank you! |
From the schema team: we haven't reached a conclusion on this topic yet, but in any case, we will likely not be depreciating any elements in the upcoming release, which will be version 2.1. This question would likely fall under a category of major revision, meaning it would be under consideration for version 3.0. Regarding the vocabularies: there is a recommendation that has been shared internally throughout the PBCore Advisory Subcommittee. We will be sharing those recommendations publicly in January. |
EBUCore has one singular Role Code, which you can find here: http://www.ebu.ch/metadata/cs/web/ebu_RoleCodeCS_p.xml.htm
It is very lengthy and detailed and separates different types of roles into broader and narrower terms.
I think this is a good idea given that we have many types of PBCore users whose creator, contributor, and publisher roles may be more specific to their collections.
The text was updated successfully, but these errors were encountered: