[CODE4LIB] Representing copyright holder in MODS
So far as I can make out from the element descriptions at http://www.loc.gov/standards/mods/userguide/origininfo.html and related pages, there seems to be no way to express in MODS who the copyright holder of a work is -- which seems strange, as you CAN state the copyright date. Am I missing something? (The publisher element is not the answer here, as it's not at all unusual for the copyright to be held by someone other than the publisher -- the author, for example.)
Re: [CODE4LIB] Representing copyright holder in MODS
The MODS convention is to add an accessCondition containing copyright information expressed in a more specialized schema. There's an example at: http://www.loc.gov/standards/mods/userguide/accesscondition.html The word copyright in copyrightDate in originInfo is a bit of a misdirect in this case, since copyright date is always relevant to the resource's origin but the identity of the rights holder isn't. Cheers, Ben Florin On Mon, Jun 13, 2011 at 11:46 AM, Mike Taylor m...@indexdata.com wrote: So far as I can make out from the element descriptions at http://www.loc.gov/standards/mods/userguide/origininfo.html and related pages, there seems to be no way to express in MODS who the copyright holder of a work is -- which seems strange, as you CAN state the copyright date. Am I missing something? (The publisher element is not the answer here, as it's not at all unusual for the copyright to be held by someone other than the publisher -- the author, for example.)
Re: [CODE4LIB] Representing copyright holder in MODS
On 13 June 2011 16:58, Benjamin Florin benjamin.flo...@gmail.com wrote: The MODS convention is to add an accessCondition containing copyright information expressed in a more specialized schema. There's an example at: http://www.loc.gov/standards/mods/userguide/accesscondition.html The word copyright in copyrightDate in originInfo is a bit of a misdirect in this case, since copyright date is always relevant to the resource's origin but the identity of the rights holder isn't. Many thanks for this, I don't think I would have spotted it! Any thoughts on how I might use this to express the copyright status of the item's abstract? -- Mike. Cheers, Ben Florin On Mon, Jun 13, 2011 at 11:46 AM, Mike Taylor m...@indexdata.com wrote: So far as I can make out from the element descriptions at http://www.loc.gov/standards/mods/userguide/origininfo.html and related pages, there seems to be no way to express in MODS who the copyright holder of a work is -- which seems strange, as you CAN state the copyright date. Am I missing something? (The publisher element is not the answer here, as it's not at all unusual for the copyright to be held by someone other than the publisher -- the author, for example.)
[CODE4LIB] ALA Linked Library Data Interest Group - 6/26, 10:30-12
*** With apologies for cross-posting *** The first official meeting of the new LITA/ALCTS Linked Library Data Interest Group (LLD-IG) will take place from 10:30-12 on Sunday, June 26 in Convention Center Room 265. The agenda is below, and online at http://wikis.ala.org/lita/index.php/Linkeddata We can also make time for a limited number of lightning talk style presentations of no longer than 5 minutes if you have projects or topics that you'd like to share. If you'd like to give a brief talk, please contact the interest group chairs. Agenda: 1) Report on LOD-LAM meeting 2) W3C LLD Recommendations 3) What this SIG will do... sub-groups? other activities? list of lld projects? training? wiki discussion? Our next meeting? 4) Short reports from anyone present: LLD activities, upcoming conferences/meetings, ideas... anything 5) Challenge for next time: someone to commit to bring something to show Minutes of previous informal LLD-IG meetings from ALA-2010 in Washington DC, Dublin Core 2010 in Pittsburgh, and ALA-MW-2011 in San Diego are online at: http://wikis.ala.org/lita/index.php/Linkeddata Thanks, Karen Coyle and Corey A Harper ALCTS/LITA LLD-IG Co-Chairs corey.har...@nyu.edu kco...@kcoyle.net -- Corey A Harper Metadata Services Librarian New York University Libraries 20 Cooper Square, 3rd Floor New York, NY 10003-7112 212.998.2479 corey.har...@nyu.edu
Re: [CODE4LIB] Representing copyright holder in MODS
From: Mike Taylor Any thoughts on how I might use this to express the copyright status of the item's abstract? One way, that I have heard discussed (though I don't know if anyone is doing it) is to represent the abstract as part of a related item (type = constituent). The related item could consist of just the abstract and the copyright statement. --Ray
Re: [CODE4LIB] Representing copyright holder in MODS
On 13 June 2011 18:39, Ray Denenberg, Library of Congress r...@loc.gov wrote: From: Mike Taylor Any thoughts on how I might use this to express the copyright status of the item's abstract? One way, that I have heard discussed (though I don't know if anyone is doing it) is to represent the abstract as part of a related item (type = constituent). The related item could consist of just the abstract and the copyright statement. Thanks, Ray. That makes sense, but seems a bit verbose. At the moment, since the accesscondition element's type attribute is uncontrolled, I am just using copyright for the main copyright statement and copyrightabstract for the copyright of the abstract. On 13 June 2011 17:45, Montoya, Gabriela gamont...@ucsd.edu wrote: Why not use PREMIS? Here at UCSD, we recognized that MODS was not sufficient to capture our copyright information, although we do use MODS for our descriptive metadata. Thanks for this. An interesting alternative, but not one that we can switch to at this stage. It's MODS or MODS+extensions for us. -- Mike.
[CODE4LIB] Drupal Interest Group Meeting at Annual
Colleagues, If you are heading to New Orleans for Annual, consider joining the LITA Drupal Interest Group at its official meeting on Saturday, June 25th, from 1:30-3:30 in room 242 of the Convention Center. We have four great presentations for Drupal users of all levels lined up: Ignite: A Drupal Newbie's Experiment Stacie Ledden, Communications Manager, Anythink Libraries The eXtensible Catalog's Drupal Toolkit: a Discovery Interface to Address Users' Needs Jennifer Bowen, Assistant Dean, University of Rochester River Campus Libraries Libraries Going Mobile with Drupal Katherine Lynch, Library Webmaster, Drexel University Libraries Using RSS, Feeds and Feeds XPath Parser to Inject Dynamic Content on a Mobile Site Laura Wiegand, Information Systems Librarian, University of North Carolina Wilmington For full presentation descriptions, please see the post on ALA Connect: http://connect.ala.org/node/144883 Hope to see you there! Nina Nina McHale, MA/MSLS Assistant Professor, Web Librarian University of Colorado Denver, Auraria Library Facebook Twitter: ninermac http://milehighbrarian.net
[CODE4LIB] Job Posting: (non-Marc) Metadata Librarian, Univ. of Virginia
Job Posting: (non-Marc) Metadata Librarian, Univ. of Virginia Link to Job Ad: http://jobs.virginia.edu/applicants/Central?quickFind=64297 The University of Virginia Library is seeking an individual who can provide metadata expertise and serve as the primary resource on non-MARC metadata design, structure and standards for the Library, as well as the larger university community. The incumbent will establish, document and maintain metadata policies, as appropriate; coordinate the translation of metadata between formats and participate in the integration of metadata from a variety of sources for search and display. This individual will also collaborate in the design and implementation of projects, workflows, and training involving non-MARC metadata, and create, edit, and manipulate metadata for resource description in the digital repository, library catalog, and other resources. Education: Master Degree in Library/Information science or other Master degree. Required: At least two years of practical experience with non-MARC metadata in a library environment. Demonstrated experience with multiple relevant XML-based standards (e.g. Dublin Core, MODS, VRA Core, METS, PREMIS). Demonstrated leadership or project management experience in a work setting. Demonstrated ability to work collaboratively across groups to achieve objectives. Excellent written and oral communication skills. Excellent interpersonal skills. Preferred: Knowledge of digital repository systems. Demonstrated experience in the transformation of XML documents using XSLT. Knowledge of linked data and semantic web concepts. Knowledge of current cataloging rules, standards and Library of Congress subject headings. You have the ability to understand how metadata is mapped and transformed as it travels between discovery, delivery and decision support systems. Salary and Benefits: Competitive depending on qualifications. This position has general faculty status with excellent benefits, including 22 days of vacation and TIAA/CREF and other retirement plans. To Apply: Review of applications will begin on July 1, 2011 and will continue until the position is filled. Applicants must apply through the University of Virginia online employment website at https://jobs.virginia.edu/ Search by position number 0607806, complete application, and attach cover letter and resume, with contact information for three current, professional references. For assistance with this process contact Al Sapienza, Director Library Human Resources at (434) 924-3081 or (434) 243-8636. The University of Virginia is an Equal Opportunity/Affirmative Action employer strongly committed to achieving excellence through cultural diversity. The University actively encourages applications and nominations from members of underrepresented groups.
[CODE4LIB] stemming in author search?
In a Solr-based search, stemming is done at indexing time, into fields with
stemmed tokens.
It seems typical in library-catalog type applications based on Solr to have the
default (or even only) searches be over these stemmed fields, thus
'auto-stemming' to the user. (Search for 'monkey', find 'monkeys' too, and vice
versa).
I am curious how many people, who have Solr based catalogs (that is, I'm
interested in people who have search engines with majority or only content
originally from MARC), use such stemmed fields ('auto-stemming') over their
_author_ fields as well.
There are pro's and con's to this. There are certainly some things in an author
field that would benefit from stemming (mostly various kinds of corporate
authors, some of whose endings end up looking like english language phrases).
There are also very many things in an author field that would not benefit from
stemming, and thus when stemming is done it sometimes(/often?) results in false
matches, pluralizing an author's last name in an inappropriate way for
instance.
So, wanna say on the list, if you are using a Solr-based catalog, are you using
stemmed fields for your author searches? Curious what people end up doing. If
there are any other more complicated clever things you've done than just
stem-or-not, let us know that too!
Jonathan
