WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsYeah! I've just tried out the Citation authority...it works well.
One way I used it: to include a concept on a cataloging record, then
attribute that concept (idea) to a written source. When browsing the record
later, as a different user might, I found it easy to "look up" the source
of the idea (as I would check a footnote or endnote in a book) by
navigating from cataloging record to concept record, and then from concept
record to citation record, via the Terms Used section of the righthand
sidebar.
I'm interested to know: does the list of values in Term Type come from a
standard? (I don't see any source mentioned in the app-layer config code in
base-instance-vocabularies.xml on the CSPACE-6008 branch in GitHub.)
Because Term Type is a dynamic list, users can modify it at will.
Remember, though, there's no way at present to specify through the UI a
standardized database value for an option.
On the other hand, IF THIS DOESN'T DRAW FROM A STANDARD, I'll add a comment
about the 'id=""' values in the vocab-citationtermtype instance: We've
found in the UC Berkeley deployments that the values stored in the database
are often visible to the end user through a report or a webapp -- something
that can't access the UI layer's message bundle strings. For that reason,
we'd prefer the saved values (the ones in the 'id=' attribute) to be
equivalent, as much as possible, to the value displayed in the UI. For
example, "Exhibition Catalog", rather than "catalog" or even
"exhibitioncatalog"; "Birth Certificate" rather than "birthcert".
Small potatoes, perhaps. Thanks for the contribution!
Rick
Hi Rick and all,
Thanks for all the positive feedback we've received regarding the Citation Authority.
Regarding the Term Type list values; in the UCB schema there is a reference to Getty's CDWA (Categories for the Description of Works of Art): http://www.getty.edu/research/publications/electronic_publications/cdwa/23related.html#RTFToC3 and this is where the list values come from. They are referred to as examples and in the Terminology/Format section there are references to several standards; so I don't think the list derives from any one fixed standard.
Cheers,
Kim
Kim Brasen
Museumsinspektør / Curator
Statens Museum for Kunst
T/M +45 2552 7144
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Rick Jaffe
Sendt: 30. maj 2013 21:21
Til: CollectionSpace Talk List
Emne: [Talk] New Citation authority
Yeah! I've just tried out the Citation authority...it works well.
One way I used it: to include a concept on a cataloging record, then attribute that concept (idea) to a written source. When browsing the record later, as a different user might, I found it easy to "look up" the source of the idea (as I would check a footnote or endnote in a book) by navigating from cataloging record to concept record, and then from concept record to citation record, via the Terms Used section of the righthand sidebar.
I'm interested to know: does the list of values in Term Type come from a standard? (I don't see any source mentioned in the app-layer config code in base-instance-vocabularies.xml on the CSPACE-6008 branch in GitHub.) Because Term Type is a dynamic list, users can modify it at will. Remember, though, there's no way at present to specify through the UI a standardized database value for an option.
On the other hand, IF THIS DOESN'T DRAW FROM A STANDARD, I'll add a comment about the 'id=""' values in the vocab-citationtermtype instance: We've found in the UC Berkeley deployments that the values stored in the database are often visible to the end user through a report or a webapp -- something that can't access the UI layer's message bundle strings. For that reason, we'd prefer the saved values (the ones in the 'id=' attribute) to be equivalent, as much as possible, to the value displayed in the UI. For example, "Exhibition Catalog", rather than "catalog" or even "exhibitioncatalog"; "Birth Certificate" rather than "birthcert".
Small potatoes, perhaps. Thanks for the contribution!
Rick