[CODE4LIB] Survey of new media research practices and preferences
Dear list, I'm writing to invite your participation in a digital media art preservation project currently underway at Cornell University. This project aims to develop scalable preservation strategies for complex, interactive, born-digital media artworks, using the collections of Cornell's Rose Goldsen Archive of New Media Art as a test bed. In developing a preservation framework that will address the needs of the broadest range of archive users, we seek the input of artists, researchers, educators, curators, and others who work with interactive digital artworks and artifacts. Would you please take a few minutes to respond to this questionnairehttps://cornell.qualtrics.com/SE/?SID=SV_6mPEBGQWr2K4nmR about your practices? (https://cornell.qualtrics.com/SE/?SID=SV_6mPEBGQWr2K4nmR) Depending on your responses, we estimate that this questionnaire will take 10-25 minutes to complete. Information about questionnaire results will be published and made available to the broader media archives community. Read more about this preservation initiative herehttp://news.cornell.edu/stories/2013/02/humanities-grant-helps-library-preserve-digital-art, or feel free to contact me at m...@cornell.edumailto:m...@cornell.edu for more information. Many thanks for your help with this investigation, and apologies for any cross-postings. Yours on behalf of the project team, Madeleine Casad Associate Curator, The Rose Goldsen Archive of New Media Art Curator for Digital Scholarship, DSPS Cornell University Library
[CODE4LIB] SCAPE Training: Preserving Your Preservation Tools, 26-27 March, The Hague
* Apologies for cross-posting * SCAPE Training: Preserving Your Preservation Tools (Package Management) 26-27 March 2014 The Hague Registration is now open for the next SCAPE Project Training event: https://scape-preserving-tools.eventbrite.co.uk. Overview Learning to Think Like a Package Maintainer Lots of great digital preservation applications and services exist, however very few are actively maintained and thus preserved! This is a big problem! By introducing the steps to develop these and engage the support of the community, this training course addresses what can be done to improve this situation. You will learn how to prepare packages for submission into the very heart of many digital environments; the operating system and directly associated “app-stores”. Attendees will be given hands-on experience with developing and maintaining packages rather than software and key differences will be discussed and evaluated. Better preservation of preservation tools, means better preservation our digital history. Learning Outcomes (by the end of the training event the attendees will be able to): 1. Understand the complexities of package management and distinguish between the different practices relating to both package objectives and chosen programming language. 2. Be able to carry out advanced package management operations in order to critically appraise current packages and propose changes. 3. Understand the importance of clearly defined versioning and licenses and the role of clear documentation and examples. 4. Apply best practice techniques in order to create a simple package suitable for long term maintenance. 5. Evaluate a number of options for managing package configuration and behaviour relating to package installation, removal, upgrade and re-installation. 6. Analyse opportunities for automating package management and releases, maintaining a clear focus on the user and not the developer. 7. Critically evaluate opportunities to generalise package management to allow the easy building and maintenance of packages on multiple platforms. 8. Assess the potential to apply package management techniques in your own environment. Agenda The agenda is available here: http://wiki.opf-labs.org/display/SP/Agenda+-+Preserving+Your+Preservation+Tools The event will be conducted in English. Who should attend? Software and tool developers, system administrators - No digital preservation knowledge required - Learn how to make your software sustainable so it is easily distributed, installed, and used Further information Travel and accommodation advice can be found on the event wiki page: http://wiki.opf-labs.org/display/SP/SCAPE+Training+Event+-+Preserving+Your+Preservation+Tools. Please note there is another major conference taking place in The Hague at the same time - we advise booking accommodation ASAP. To find out more about the SCAPE Project visit: http://www.scape-project.eu/. Save the date! SCAPE OPF Executive Seminar: Managing Digital Preservation, 25 March, The Hague. Registration opening soon. Kind Regards, Rebecca McGuinness SCAPE Project Training Lead
[CODE4LIB] Web Design Firm Recommendation Needed
***Cross-posted to Web4Lib apologies in advance if you have to read this more than once!*** Williams College Libraries may have the opportunity to hire a web design firm to design and possibly implement in Drupal the front page and template pages for the user interface of our new institutional repository. Has anyone outsourced such design work for their institutional repository or other web projects and have recommendations for good firms? Thanks for any recommendations! Lori --- Lori DuBois Reference and Instruction Librarian Williams College Libraries Williamstown, MA
Re: [CODE4LIB] [WEB4LIB] Web Design Firm Recommendation Needed
I recommend Influx: Library User Experience. http://weareinflux.com/ -Original Message- From: Web technologies in libraries [mailto:web4...@listserv.nd.edu] On Behalf Of Lori DuBois Sent: Wednesday, January 22, 2014 9:42 AM To: web4...@listserv.nd.edu Subject: [WEB4LIB] Web Design Firm Recommendation Needed ***Cross-posted to Code4Lib apologies in advance if you have to read this more than once!*** Williams College Libraries may have the opportunity to hire a web design firm to design and possibly implement in Drupal the front page and template pages for the user interface of our new institutional repository. Has anyone outsourced such design work for their institutional repository or other web projects and have recommendations for good firms? Thanks for any recommendations! Lori --- Lori DuBois Reference and Instruction Librarian Williams College Libraries Williamstown, MA To unsubscribe: http://bit.ly/web4lib Web4Lib Web Site: http://web4lib.org/ 2014-01-22
Re: [CODE4LIB] [WEB4LIB] Web Design Firm Recommendation Needed
I would recommend the firm I used to work for Viget http://viget.com/. They've done a number of university websites (upenn http://www.upenn.edu/, lafayette college http://www.lafayette.edu/). They are a bit pricey but the people are great. And if you are interested, ping me and I can introduce you to the best sales guy on the planet (no i'm serious, best sales guy ever). On Wed, Jan 22, 2014 at 9:21 AM, Michael Schofield mschofi...@nova.eduwrote: I recommend Influx: Library User Experience. http://weareinflux.com/ -Original Message- From: Web technologies in libraries [mailto:web4...@listserv.nd.edu] On Behalf Of Lori DuBois Sent: Wednesday, January 22, 2014 9:42 AM To: web4...@listserv.nd.edu Subject: [WEB4LIB] Web Design Firm Recommendation Needed ***Cross-posted to Code4Lib apologies in advance if you have to read this more than once!*** Williams College Libraries may have the opportunity to hire a web design firm to design and possibly implement in Drupal the front page and template pages for the user interface of our new institutional repository. Has anyone outsourced such design work for their institutional repository or other web projects and have recommendations for good firms? Thanks for any recommendations! Lori --- Lori DuBois Reference and Instruction Librarian Williams College Libraries Williamstown, MA To unsubscribe: http://bit.ly/web4lib Web4Lib Web Site: http://web4lib.org/ 2014-01-22
[CODE4LIB] elsevier EFFECT41
I was wondering if anyone has worked with the Elsevier EFFECT41 datasets (http://info.sciencedirect.com/techsupport/sdos/effect41.pdf) I've written a parser which mostly works fine then discovered their notion of continuation lines (e.g. any line which does not start with a tag is a continuation of the previous line). I could continue working on what I've got and try to figure out how to handle the continuation lines, but I was hoping that someone might have already done something that joins continuation lines. Please followup to ja...@cornell.edumailto:ja...@cornell.edu
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
I'm still pretty new at this linked data thing, but I find it strange that RDA element properties URIs such as http://rdaregistry.info/Elements/a/P50034 and http://rdaregistry.info/Elements/a/P50209 both return the same HTML page in a browser. Would it not have been more usable if the properties used hash-URIs that could have located the particular property on the particular page (e.g. http://rdaregistry.info/Elements/a#P50034)? Also, a plain curl request returns Content-type: application/octet-stream -- but it's pretty clearly Turtle, so I think that should be Content-type: text/turtle I would have liked to see more meaningful URIs--like http://rdaregistry.info/Elements/agent/addressOf instead of http://rdaregistry.info/Elements/a/P50209--as meaningful URIs seem a lot more approachable to this non-machine, but I guess that would have been a lot more work. On Tue, Jan 21, 2014 at 10:45 AM, Diane Hillmann metadata.ma...@gmail.com wrote: Folks: I hope this announcement will be of general interest (and apologies if you receive more than one). Diane -- Forwarded message -- From: JSC Secretary jscsecret...@rdatoolkit.org Date: Tue, Jan 21, 2014 at 10:23 AM Subject: [rules] Publication of the RDA Element Vocabularies snip recipients RDA colleagues, See the announcement below, also posted on the JSC website. Feel free to share this information with your colleagues. Regards, Judy Kuhagen = = = = = The Joint Steering Committee for Development of RDA (JSC), Metadata Management Associates, and ALA Publishing (on behalf of the co-publishers of RDA) are pleased to announce that the RDA elements and relationship designators have been published in the Open Metadata Registry (OMR) as Resource Description Framework (RDF) element sets suitable for linked data and semantic Web applications. The elements include versions unconstrained by Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD), the standard library models underpinning RDA, that are intended for use in applications by non-RDA communities. The published version of the RDA element sets builds on several years of work by the DCMI/RDA Task Group. Earlier versions developed by the Group will remain available, but will be deprecated for further development and use, and redirected to the new version. Gordon Dunsire, Chair of the JSC, said The RDA element set is a distillation of modern approaches to resource discovery supporting rich descriptions of library and cultural heritage materials and detailed relationships between them at international level. The JSC has recently established a working group to assist in extending and refining the RDA elements, and hopes that they will be useful to other communities, ranging from close neighbours in library linked data to the global networks of general search. Diane Hillmann of Metadata Management Associates said We are extremely pleased to be able to make this new version available now in fully published form, ready for implementation by libraries and vendors. We look forward to discussing the important features available in this version with our colleagues at the upcoming ALA Midwinter meetings and beyond. James Hennelly, Managing Editor of RDA Toolkit, said This is an important update to the RDA Registry and a crucial step in the advancement of RDA's mission to be a standard that is accessible to both cataloging professionals, through the toolkit and print and ebook publications, and to application developers seeking to make use of library data, through the Registry's expression of the RDA elements and vocabularies. The basic RDA element set namespace is rdaregistry.info and it contains a total of over 1600 properties and classes. Elements are distributed in sets (the number of elements in each set is given in brackets): Agent properties [http://metadataregistry.org/schema/show/id/81.html]http://metadataregistry.org/schema/show/id/81.html(226) Expression properties [http://metadataregistry.org/schema/show/id/78.html]http://metadataregistry.org/schema/show/id/78.html(236) Item properties [http://metadataregistry.org/schema/show/id/80.html]http://metadataregistry.org/schema/show/id/80.html(54) Manifestation properties [http://metadataregistry.org/schema/show/id/79.html]http://metadataregistry.org/schema/show/id/79.html(213) Work properties [http://metadataregistry.org/schema/show/id/77.html]http://metadataregistry.org/schema/show/id/77.html(232) Unconstrained properties [http://metadataregistry.org/schema/show/id/82.html]http://metadataregistry.org/schema/show/id/82.html(698) Classes [http://metadataregistry.org/schema/show/id/83.html]http://metadataregistry.org/schema/show/id/83.html(8) Follow the links to see details of each element set. Questions or comments on the content of the element sets may be addressed to the Chair of the JSC, Gordon Dunsire
[CODE4LIB] Job: Dryad Librarian at University of North Carolina at Chapel Hill
Dryad Librarian University of North Carolina at Chapel Hill Chapel Hill Dryad (http: datadryad.org) is a curated general-purpose repository that makes the data underlying scientific publications discoverable, freely reusable, and citable. The Dryad team works with stakeholders from journals and scientific societies to develop data sharing policies and ensure the long-term sustainability of the repository. The Dryad project is seeking a detail- oriented person with good analytical and communication skills. This position performs a variety of curatorial and metadata-specific tasks, manages assistant curators, collaborates with Dryad development team members to improve curatorial procedures, and advises on future design and testing of repository system functionalities. Minimum Qualifications: Required Qualifications: * Experience with library cataloging and metadata standards, such as Dublin Core (DC), Darwin Core (DwC), Ecological Metadata Language (EML), or the Anglo-American Cataloging Rules (AACR2). * Working knowledge of metadata principles, authority control practices, controlled vocabularies, and classification systems. * Exposure to scientific data and data repositories. * Demonstrated experience with project management, including planning, documentation, and team leadership. * Critical thinking skills, including individual and collaborative problem-solving. * Excellent written and verbal communication skills. Desired Qualifications: * Background in research science. * Knowledge of the Semantic Web, linked data, and knowledge organization systems. * Exposure to metadata models, such as the Resource Description Framework (RDF), Functional Requirements for Bibliographic Records (FRBR), and Open Archives Initiative Protocol-Object Exchange and Reuse (OAI-ORE). * Exposure to digital curation practices and data life-cycle management. * Knowledge of digital preservation standards and best practices.Masters degree (MSLS/MLS or MSIS/MIS) from an ALA accredited program Brought to you by code4lib jobs: http://jobs.code4lib.org/job/11651/
[CODE4LIB] Job: Social Sciences Data Librarian at Colby College
Social Sciences Data Librarian Colby College Waterville Colby College Libraries invites applications for a social sciences data librarian in Scholarly Resources Services (SRS). Within the Colby Libraries, the SRS group's primary mission is to support faculty and student research in an innovative teaching and learning environment. To that end, the successful candidate will work closely as liaison to departments in the social sciences, providing data and statistical support, information literacy and research instruction, individual consultations, and assistance in collection development in an increasingly digital environment. Preferred start date is July 1, 2014. Applicants should address their materials to the chair of the Search Committee, Susan Cole, and send the following electronically in PDF format to Stephanie Frost ([sjfr...@colby.edu](mailto:sjfr...@colby.edu)). A cover letter Curriculum vitae A statement of teaching philosophy Graduate transcripts Three letters of recommendation Required Qualifications: An ALA- accredited master's degree or international equivalent Evidence of a commitment to information literacy and library instruction Evidence of broad knowledge in the social sciences Flexibility, creativity, energy, and ability to work in a changing environment, and to work collaboratively as a member of a goal-oriented team Evidence of excellent communication and analytical skills Preferred Qualifications: Teaching experience in an academic setting Experience working with data sets and knowledge of research practices relating to data Knowledge of significant trends and issues in research support and data management; familiarity with one or more institutional or disciplinary repositories and experience using statistical software in work with data sets Subject knowledge of economics and government, including collection development Colby is a highly selective liberal arts college located in central Maine. The Colby College Libraries are central to scholarship and a key part of the Colby academic program. There are three libraries with a professional staff of 13 librarians. Colby librarians are faculty without rank, eligible for sabbaticals and are expected to contribute to creative, scholarly, and professional activities, and to participate in library-wide and campus-wide service. A significant staff reorganization in 2012 resulted in the Libraries being poised for transformational change in the provision of services, instruction, and collections. For more information about the Libraries, visit [www.colby.edu/library](http://www.colby.edu/library). Colby College is committed to equality and diversity and is an equal opportunity employer. We encourage inquiries from candidates who will contribute to the cultural and ethnic diversity of our college. Colby College does not discriminate on the basis of race, gender, sexual orientation, disability, religion, ancestry or national origin, or age in employment or in our educational programs. For more information about the College, please visit our website: [www.colby.edu](http://www.colby.edu). Brought to you by code4lib jobs: http://jobs.code4lib.org/job/11654/
[CODE4LIB] Job: Archival Processing Specialist at University of California, Santa Barbara
Archival Processing Specialist University of California, Santa Barbara Santa Barbara Under the direction of the Head, Special Collections and in coordination with collection curators, the Archival Processing Specialist has full responsibility for the uniform arrangement and description standards for the processing of collections. Establishes processing plans for collections, processes complex collections, trains and supervises students in the processing of simple collections, creates indexes, container lists, and finding guides. Using Archivists' Toolkit, accessions collections, and encodes collection finding guides in Encoded Archival Description (EAD). Maintains and updates collection records in Archivists' Toolkit and republishes guides as needed. Works with catalogers in cataloging collections and assists metadata and Digitization Center staff with collections being digitized. Provides coverage of service point as needed and provides reference services as needed. The Archival Processing Specialist uses independent judgement and works with minimal supervision. Minimum Requirements * Bachelor's or equivalent combination of education and experience * Knowledge of library and archival systems and procedures including experience with Archivists' Toolkit and Encoded Archival Description * Excellent interpersonal as well as written and oral communications skills * Demonstrated aptitude for accuracy and attention to detail * High level of computer literacy with standard office productivity software * Demonstrated initiative and proven ability to work independently and in a team environment Desirable Requirements * Experience with Filemaker pro, UCSB library catalog, Online Archive of California, and familiarity with ArchivesSpace * Experience working in a supervisory capacity * Experience working with databases, content management, scanning and other software Special Conditions of Employment * A little help? Go to Driver's License Requirements or Background Check Guidelines Satisfactory completion of a fingerprint background check Brought to you by code4lib jobs: http://jobs.code4lib.org/job/11662/
[CODE4LIB] Job: Senior Linux Systems Engineer at United States National Agricultural Library
Senior Linux Systems Engineer United States National Agricultural Library Beltsville The National Agricultural Library is now recruiting for a senior level Linux Systems Engineer. The announcement will close on Friday, January 31, 2014. Complete vacancy announcement information and application instructions are posted on USAJOBS: [https://www.usajobs.gov/GetJob/ViewDetails/358520300](https://www.usajobs.gov /GetJob/ViewDetails/358520300) Job Announcement Number: DEU-14-1014938-AMN; Control Number: 358520300. This position is in the Systems Technology Branch, which is responsible for managing National Agricultural Library (NAL) enterprise servers and networking; operating the NAL data center with its associated telecommunications and related support equipment; providing and supporting local area network services, desktop equipment, and end-used software; and tracking and resolving reported problems. The incumbent will serve as a senior Linux Systems Engineer and is responsible for managing web applications, web services, and Java EE applications on virtualized and consolidated server/storage infrastructure. Duties: * Manages web applications on virtualized and consolidated server/storage infrastructure * Provides technical advice to management in setting technical direction * Conducts analyses, develops plans and procedures, and configures tools and systems * Installs new or modified hardware and operating systems and applications software * Installs and integrates systems fixes, updates, and enhancements * Evaluates the impact of proposed applications on the operating environment and recommends changes to ensure its functionality and stability * Manages resources to ensure and improve systems performance, capacity, availability, serviceability, and recoverability * Monitors and troubleshoots systems administration methods and procedures * Develops and documents systems administration methods and procedures * Ensures rigorous application of information security principles and practices in the management of IT systems Brought to you by code4lib jobs: http://jobs.code4lib.org/job/11671/
[CODE4LIB] Job: Film Archivist at Indiana University Bloomington
Film Archivist Indiana University Bloomington Bloomington Reporting to Director of IU Libraries' Film Archive: provide reference services and research consultations, support to faculty, students, staff, community at large; assist with collection development, management, inventorying; inspect and prepare films for patron use, digitization and projection; assist with grant proposals and project management; manage and develop preservation projects, online exhibits, collaborative national collection related projects; assist with prioritizing of cataloging/conservation/preservation of film collections; keep abreast of developments related to moving image archiving, digital collection management and related issues; contribute to developments in the field of moving image archives through active professional engagement and research, presenting and publishing in appropriate venues. Qualifications: Required: ALA-accredited Master's degree in Library Science (MLS) or equivalent education or experience; demonstrated knowledge and understanding of film, video, digital moving image formats and preservation issues; ability to work in team environment and build working relationships with campus colleagues; excellent interpersonal skills, ability to work well with diverse populations of faculty, students, researchers, academic colleagues; experience in collection development and broad knowledge of information resources for moving image collections; experience in moving image archives including motion picture film-handling experience; excellent communication skills; ability to meet requirements of tenure-track librarian position. Salary and Benefits: Salary competitive and commensurate with experience and education; benefits include university healthcare plan, university-funded base retirement plan, 100% university paid group life insurance plan, generous paid time off plan. This tenure-track academic appointment includes eligibility for sabbatical leaves. To apply: For full consideration, applications must be received prior to February 17, 2014. For complete copy of posting with additional responsibilities, qualifications, etc., go to ww w.libraries.iub.edu/index.php?pageId=1410. Interested candidates should review the application requirements and submit their application at: https://indiana.peopleadmin.com. Brought to you by code4lib jobs: http://jobs.code4lib.org/job/11692/
Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options
How about skip the pricey touchscreen and do a Johnny Lee: http://johnnylee.net/projects/wii/ I.e. use a Wii or Kinect controller to enable gesture functions on a regular screen. It's on the to-do list I can never get to. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Andrew Gordon Sent: Wednesday, January 22, 2014 9:46 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Digital Collections Browser Kiosk Software Options Hi All, We are looking into options for setting up a physical kiosk (touchscreen monitor and computer) in our lobby to allow visitors to our building to browse digital versions of some items from our collection. I see that Turning The Pages (e.g. http://archive.nlm.nih.gov/proj/ttp/) provides a nice solution for this but I just wanted to see if anyone else had worked with something similar and might know of any other options (open source?) so that we can do a little comparing and contrasting. For some reason I am thinking there was a discussion a little while back about 3D digital collections browsing but can't seem to locate it and don't know it if was like the above scenario. I think since it's a kiosk style implementation and we are looking for apples-to-apples comparisons, we are interested in the physical, touch-screen turning of the page interaction rather than a browser pointed at a more pragmatic digital collections browser, at least at this point in the exploration. Thanks in advance for anyone that might have potential suggestions, -d Andrew Gordon, MSI Systems Librarian Center for the History of Medicine and Public Health New York Academy of Medicine 1216 Fifth Avenue New York, NY, 10029 212.822.7324 http://nyamcenterforhistory.org/
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
I can't address the first points, but I can speak a bit to the question of meaningful URIs. In the original creation of the RDA elements, meaningful URIs were used based on the actual RDA terminology. This resulted in URIs like: http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequence and... http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequenceManifestation Not only that, the terminology for some elements changed over time, which in some cases meant deprecating a property that was then overly confusing based on its name. Now, I agree that one possibility would have been for the JSC to develop meaningful but reasonably short property names. Another possibility is that we cease looking at URIs and begin to work with labels, since URIs are for machines and labels are for humans. Unfortunately, much RDF software still expects you to work with the underlying URI rather than the human-facing label. We need to get through that stage as quickly as possible, because it's causing us to put effort into URI naming that would be best used for other analysis activities. kc On 1/22/14, 9:57 AM, Dan Scott wrote: I'm still pretty new at this linked data thing, but I find it strange that RDA element properties URIs such as http://rdaregistry.info/Elements/a/P50034 and http://rdaregistry.info/Elements/a/P50209 both return the same HTML page in a browser. Would it not have been more usable if the properties used hash-URIs that could have located the particular property on the particular page (e.g. http://rdaregistry.info/Elements/a#P50034)? Also, a plain curl request returns Content-type: application/octet-stream -- but it's pretty clearly Turtle, so I think that should be Content-type: text/turtle I would have liked to see more meaningful URIs--like http://rdaregistry.info/Elements/agent/addressOf instead of http://rdaregistry.info/Elements/a/P50209--as meaningful URIs seem a lot more approachable to this non-machine, but I guess that would have been a lot more work. On Tue, Jan 21, 2014 at 10:45 AM, Diane Hillmann metadata.ma...@gmail.com wrote: Folks: I hope this announcement will be of general interest (and apologies if you receive more than one). Diane -- Forwarded message -- From: JSC Secretary jscsecret...@rdatoolkit.org Date: Tue, Jan 21, 2014 at 10:23 AM Subject: [rules] Publication of the RDA Element Vocabularies snip recipients RDA colleagues, See the announcement below, also posted on the JSC website. Feel free to share this information with your colleagues. Regards, Judy Kuhagen = = = = = The Joint Steering Committee for Development of RDA (JSC), Metadata Management Associates, and ALA Publishing (on behalf of the co-publishers of RDA) are pleased to announce that the RDA elements and relationship designators have been published in the Open Metadata Registry (OMR) as Resource Description Framework (RDF) element sets suitable for linked data and semantic Web applications. The elements include versions unconstrained by Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD), the standard library models underpinning RDA, that are intended for use in applications by non-RDA communities. The published version of the RDA element sets builds on several years of work by the DCMI/RDA Task Group. Earlier versions developed by the Group will remain available, but will be deprecated for further development and use, and redirected to the new version. Gordon Dunsire, Chair of the JSC, said The RDA element set is a distillation of modern approaches to resource discovery supporting rich descriptions of library and cultural heritage materials and detailed relationships between them at international level. The JSC has recently established a working group to assist in extending and refining the RDA elements, and hopes that they will be useful to other communities, ranging from close neighbours in library linked data to the global networks of general search. Diane Hillmann of Metadata Management Associates said We are extremely pleased to be able to make this new version available now in fully published form, ready for implementation by libraries and vendors. We look forward to discussing the important features available in this version with our colleagues at the upcoming ALA Midwinter meetings and beyond. James Hennelly, Managing Editor of RDA Toolkit, said This is an important update to the RDA Registry and a crucial step in the advancement of RDA's mission to be a standard that is accessible to both cataloging professionals, through the toolkit and print and ebook publications, and to application developers seeking to make use of library data, through the Registry's expression of the RDA elements and vocabularies. The basic RDA element set namespace is rdaregistry.info and it contains a total of over 1600 properties and classes. Elements are
Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options
On a similar note to Sam's suggestion, I saw a demo by Open Exhibits http://openexhibits.org/category/software/ of their multi-touch image browser - they just released a new version of their open-source sdk that allows use of the Leap Motion controller (or several of them for more users) - that way you can use a less expensive non-touch screen and get the same or better effect. Been meaning to try this out but the time it keeps getting away from me. Would love to hear of someone making it work. -Derek Derek Merleaux @dmer On Wed, Jan 22, 2014 at 12:45 PM, Andrew Gordon agor...@nyam.org wrote: Hi All, We are looking into options for setting up a physical kiosk (touchscreen monitor and computer) in our lobby to allow visitors to our building to browse digital versions of some items from our collection. I see that Turning The Pages (e.g. http://archive.nlm.nih.gov/proj/ttp/) provides a nice solution for this but I just wanted to see if anyone else had worked with something similar and might know of any other options (open source?) so that we can do a little comparing and contrasting. For some reason I am thinking there was a discussion a little while back about 3D digital collections browsing but can't seem to locate it and don't know it if was like the above scenario. I think since it's a kiosk style implementation and we are looking for apples-to-apples comparisons, we are interested in the physical, touch-screen turning of the page interaction rather than a browser pointed at a more pragmatic digital collections browser, at least at this point in the exploration. Thanks in advance for anyone that might have potential suggestions, -d Andrew Gordon, MSI Systems Librarian Center for the History of Medicine and Public Health New York Academy of Medicine 1216 Fifth Avenue New York, NY, 10029 212.822.7324 http://nyamcenterforhistory.org/
[CODE4LIB] Job opening: Systems and Technology Librarian
Reporting to the AVP, Computer Services, the Health Sciences Libraries (HSL) Systems Technology Librarian is responsible for the Libraries' IT strategy, development and daily operations. The Health Sciences Libraries include the Ginsburg Health Sciences Library on Temple's Health Sciences Campus and the Krausz Library of Podiatric Medicine in Center City Philadelphia.This position will direct,supervise, and coordinate the operations of the IT department - including management of staff, installation and support of public and staff desktop computers and peripherals, supporting university-wide library-specific system applications, and reviewing and recommending new technology and technology-related services in the Libraries. The Systems Technology Librarian plays an essential role in shaping the Health Sciences Libraries IT environment, and the enhancement of the Libraries' services through a wide range of technologies and systems. This position will also play a role as a team member in the development and maintenance of central or shared library systems used throughout the entire Temple University Libraries' system. Performs other duties as assigned. Required Education and Experience: ALA accredited MLS and two years IT-related experience. Required Skills and Abilities: - Demonstrated ability to identify, diagnose and resolve technical problems in a significant IT environment. - Familiarity with library systems such as integrated library systems and interlibrary loan systems. - Demonstrated evidence of continuing education/professional development in IT programs or computers in libraries applications. - Experience installing and configuring PC and Mac workstations. - Demonstrated knowledge of Microsoft office programs, networking and information security products. - Demonstrated project management skills, with the ability to manage multiple projects simultaneously. - Ability to work independently and as part of a team. Preferred: - Experience providing IT support in a large university library or health sciences library environment. - Help Desk management experience; experience with ticketing/tracking systems such as Remedy. - Experience supervising full-time and/or part-time student staff. - Experience with open source library software, including use, development, and implementation. - Experience providing training and creating documentation Please visit our website at www.temple.edu, scroll to the bottom of the page and click on Careers @ Temple. Please reference TU-17373. AA, EOE, m/f/d/v. -- Delphine Khanna, Head of Digital Library Initiatives Temple University Library (http://library.temple.edu) Samuel L. Paley Library, Room 113, 1210 Polett Walk, Philadelphia, PA 19122 Tel: 215-204-4768 | Fax: 215-204-5201 | Email: delph...@temple.edu
Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options
On Jan 22, 2014, at 11:16 AM, Sam Kome sam_k...@cuc.claremont.edu wrote: How about skip the pricey touchscreen and do a Johnny Lee: http://johnnylee.net/projects/wii/ I.e. use a Wii or Kinect controller to enable gesture functions on a regular screen. It's on the to-do list I can never get to. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Andrew Gordon Sent: Wednesday, January 22, 2014 9:46 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Digital Collections Browser Kiosk Software Options Hi All, We are looking into options for setting up a physical kiosk (touchscreen monitor and computer) in our lobby to allow visitors to our building to browse digital versions of some items from our collection. I see that Turning The Pages (e.g. http://archive.nlm.nih.gov/proj/ttp/) provides a nice solution for this but I just wanted to see if anyone else had worked with something similar and might know of any other options (open source?) so that we can do a little comparing and contrasting. For some reason I am thinking there was a discussion a little while back about 3D digital collections browsing but can't seem to locate it and don't know it if was like the above scenario. I think since it's a kiosk style implementation and we are looking for apples-to-apples comparisons, we are interested in the physical, touch-screen turning of the page interaction rather than a browser pointed at a more pragmatic digital collections browser, at least at this point in the exploration. Thanks in advance for anyone that might have potential suggestions, -d Andrew Gordon, MSI Systems Librarian Center for the History of Medicine and Public Health New York Academy of Medicine 1216 Fifth Avenue New York, NY, 10029 212.822.7324 http://nyamcenterforhistory.org/
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
Hi Karen: On Wed, Jan 22, 2014 at 3:16 PM, Karen Coyle li...@kcoyle.net wrote: I can't address the first points, but I can speak a bit to the question of meaningful URIs. In the original creation of the RDA elements, meaningful URIs were used based on the actual RDA terminology. This resulted in URIs like: http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequence and... http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequenceManifestation Not only that, the terminology for some elements changed over time, which in some cases meant deprecating a property that was then overly confusing based on its name. Now, I agree that one possibility would have been for the JSC to develop meaningful but reasonably short property names. Another possibility is that we cease looking at URIs and begin to work with labels, since URIs are for machines and labels are for humans. Unfortunately, much RDF software still expects you to work with the underlying URI rather than the human-facing label. We need to get through that stage as quickly as possible, because it's causing us to put effort into URI naming that would be best used for other analysis activities. Thanks for responding on this front. I understand that, while the vocabulary was in heavy active development it might have been painful to adjust as elements changed, but given that this marks the actual publication of the vocabulary, that churn should have settled down, and then this part of the JSC's contribution to semantic web could have semantics applied at both the micro and macro level. I guess I see URIs as roughly parallel to API names; as long as humans are assembling programs, we're likely to benefit from having meaningful (no air quotes required) names... even if sometimes the meaning drifts over time and the code APIs need to be refactored. Dealing with sequentially numbered alphanumeric identifiers reminds me rather painfully of MARC. For what it's worth (and it might not be worth much) curl http://rdaregistry.info/Elements/a/P50101 | grep reg:name | sort | uniq -c shows that the reg:name property is unique across all of the agent properties, at least. Remnants of the earlier naming effort? If that pattern holds, those could have been simply used for the identifiers in place of P#. The most unwieldy of those appears to be otherDesignationAssociatedWithTheCorporateBody (which _is_ unwieldy, certainly, but still more meaningful than http://rdaregistry.info/Elements/a/P50033). Perhaps it's not too late?
[CODE4LIB] code4lib Los Angeles meetup Feb 20th at USC
The Known Knowns What: A meeting where L.A.-based library techies can meet, talk shop, and learn from each other. When: Thursday, February 20th, 2014, 3pm-4:30pm Where: Herklotz Room, Doheny Memorial Library, USC Who: anyone interested in code and libraries. *** PLEASE RSVP directly to me, off list. *** The Known Unknowns -- The Agenda is not set, but may include: -- a round table discussion of everyone's current projects, successes, and pitfalls -- one or two short (15-20 mins) presentations; a great opportunity to practice for the main code4lib event in March or some other conference. Let me know if you want to present so I can coordinate A/V setup. -- future plans for the group (best meeting times, locations, communication methods, etc.) Parking: I may be able to get attendees free parking. Details coming soon. In any case, the Metro Expo Line has a stop at USC! Happy hour: If enough people are interested (and not afraid of traffic), after the meeting we can all grab a bite and a drink at the gastropub across the street or the campus bar in the center of campus (both have good food and beer). *** Once again, PLEASE RSVP directly to me, off list. *** The Herklotz Room only fits two dozen people, so I need to keep track of potential attendance. The Unknown Knowns - Stuff I forgot to include in this message. The Unknown Unknowns ? Joshua Gomez Library Systems Programmer University of Southern California 3550 Trousdale Parkway Los Angeles, CA 90089
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
Je ne comprends pas l'anglais. Je ne comprends pas l'URI otherDesignationAssociatedWithTheCorporateBody 私は日本人です。私は理解していない、そのURI Opaque URIs with human readable labels helps in an international context. Just my two yens worth :) G - Gill Hamilton Digital Access Manager National Library of Scotland George IV Bridge Edinburgh EH1 1EW, Scotland e: g.hamil...@nls.uk t: +44 (0)131 623 3770 Skype: gill.hamilton.nls From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Dan Scott [deni...@gmail.com] Sent: 22 January 2014 21:10 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies Hi Karen: On Wed, Jan 22, 2014 at 3:16 PM, Karen Coyle li...@kcoyle.net wrote: I can't address the first points, but I can speak a bit to the question of meaningful URIs. In the original creation of the RDA elements, meaningful URIs were used based on the actual RDA terminology. This resulted in URIs like: http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequence and... http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequenceManifestation Not only that, the terminology for some elements changed over time, which in some cases meant deprecating a property that was then overly confusing based on its name. Now, I agree that one possibility would have been for the JSC to develop meaningful but reasonably short property names. Another possibility is that we cease looking at URIs and begin to work with labels, since URIs are for machines and labels are for humans. Unfortunately, much RDF software still expects you to work with the underlying URI rather than the human-facing label. We need to get through that stage as quickly as possible, because it's causing us to put effort into URI naming that would be best used for other analysis activities. Thanks for responding on this front. I understand that, while the vocabulary was in heavy active development it might have been painful to adjust as elements changed, but given that this marks the actual publication of the vocabulary, that churn should have settled down, and then this part of the JSC's contribution to semantic web could have semantics applied at both the micro and macro level. I guess I see URIs as roughly parallel to API names; as long as humans are assembling programs, we're likely to benefit from having meaningful (no air quotes required) names... even if sometimes the meaning drifts over time and the code APIs need to be refactored. Dealing with sequentially numbered alphanumeric identifiers reminds me rather painfully of MARC. For what it's worth (and it might not be worth much) curl http://rdaregistry.info/Elements/a/P50101 | grep reg:name | sort | uniq -c shows that the reg:name property is unique across all of the agent properties, at least. Remnants of the earlier naming effort? If that pattern holds, those could have been simply used for the identifiers in place of P#. The most unwieldy of those appears to be otherDesignationAssociatedWithTheCorporateBody (which _is_ unwieldy, certainly, but still more meaningful than http://rdaregistry.info/Elements/a/P50033). Perhaps it's not too late? Follow us on Twitter and Facebook National Library of Scotland, Scottish Charity, No: SCO11086 This communication is intended for the addressee(s) only. If you are not the addressee please inform the sender and delete the email from your system. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of National Library of Scotland. This message is subject to the Data Protection Act 1998 and Freedom of Information (Scotland) Act 2002. No liability is accepted for any harm that may be caused to your systems or data by this message. www.nls.uk
Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options
Very cool, did not consider these approaches but they are worth looking into. Out of curiosity, would there be good recommendations if we were to forego the touch screen requirement? Just plain ole' dumb mouse and keyboard? Thanks again, drew -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Derek Merleaux Sent: Wednesday, January 22, 2014 3:27 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options On a similar note to Sam's suggestion, I saw a demo by Open Exhibits http://openexhibits.org/category/software/ of their multi-touch image browser - they just released a new version of their open-source sdk that allows use of the Leap Motion controller (or several of them for more users) - that way you can use a less expensive non-touch screen and get the same or better effect. Been meaning to try this out but the time it keeps getting away from me. Would love to hear of someone making it work. -Derek Derek Merleaux @dmer On Wed, Jan 22, 2014 at 12:45 PM, Andrew Gordon agor...@nyam.org wrote: Hi All, We are looking into options for setting up a physical kiosk (touchscreen monitor and computer) in our lobby to allow visitors to our building to browse digital versions of some items from our collection. I see that Turning The Pages (e.g. http://archive.nlm.nih.gov/proj/ttp/) provides a nice solution for this but I just wanted to see if anyone else had worked with something similar and might know of any other options (open source?) so that we can do a little comparing and contrasting. For some reason I am thinking there was a discussion a little while back about 3D digital collections browsing but can't seem to locate it and don't know it if was like the above scenario. I think since it's a kiosk style implementation and we are looking for apples-to-apples comparisons, we are interested in the physical, touch-screen turning of the page interaction rather than a browser pointed at a more pragmatic digital collections browser, at least at this point in the exploration. Thanks in advance for anyone that might have potential suggestions, -d Andrew Gordon, MSI Systems Librarian Center for the History of Medicine and Public Health New York Academy of Medicine 1216 Fifth Avenue New York, NY, 10029 212.822.7324 http://nyamcenterforhistory.org/
Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options
There is a cross-platform web kiosk that can be locked down called Open Kiosk, is is based on Firefox and has a plethora of features. //Riley Sent from my iPhone On Jan 22, 2014, at 5:25 PM, Andrew Gordon agor...@nyam.org wrote: Very cool, did not consider these approaches but they are worth looking into. Out of curiosity, would there be good recommendations if we were to forego the touch screen requirement? Just plain ole' dumb mouse and keyboard? Thanks again, drew -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Derek Merleaux Sent: Wednesday, January 22, 2014 3:27 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Digital Collections Browser Kiosk Software Options On a similar note to Sam's suggestion, I saw a demo by Open Exhibits http://openexhibits.org/category/software/ of their multi-touch image browser - they just released a new version of their open-source sdk that allows use of the Leap Motion controller (or several of them for more users) - that way you can use a less expensive non-touch screen and get the same or better effect. Been meaning to try this out but the time it keeps getting away from me. Would love to hear of someone making it work. -Derek Derek Merleaux @dmer On Wed, Jan 22, 2014 at 12:45 PM, Andrew Gordon agor...@nyam.org wrote: Hi All, We are looking into options for setting up a physical kiosk (touchscreen monitor and computer) in our lobby to allow visitors to our building to browse digital versions of some items from our collection. I see that Turning The Pages (e.g. http://archive.nlm.nih.gov/proj/ttp/) provides a nice solution for this but I just wanted to see if anyone else had worked with something similar and might know of any other options (open source?) so that we can do a little comparing and contrasting. For some reason I am thinking there was a discussion a little while back about 3D digital collections browsing but can't seem to locate it and don't know it if was like the above scenario. I think since it's a kiosk style implementation and we are looking for apples-to-apples comparisons, we are interested in the physical, touch-screen turning of the page interaction rather than a browser pointed at a more pragmatic digital collections browser, at least at this point in the exploration. Thanks in advance for anyone that might have potential suggestions, -d Andrew Gordon, MSI Systems Librarian Center for the History of Medicine and Public Health New York Academy of Medicine 1216 Fifth Avenue New York, NY, 10029 212.822.7324 http://nyamcenterforhistory.org/
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
P166123464771 And now no one understands at all. CIDOC-CRM has taken the same approach -- it's better that everyone is equal in their non-comprehension than people who speak a particular language are somehow advantaged. BTW, as an English speaker, I also don't understand other designation associated with the corporate body, regardless of spaces or camelCase. Labels and semantic descriptions are *always* important. The we might change what this means argument is also problematic -- if you change what it means, then you should change the URI! Otherwise people will continue to use them incorrectly, plus the legacy data generated with the previous definition will suddenly change what it's saying. Finally, 1600 properties... good luck with that. Rob On Wed, Jan 22, 2014 at 3:03 PM, Hamilton, Gill g.hamil...@nls.uk wrote: Je ne comprends pas l'anglais. Je ne comprends pas l'URI otherDesignationAssociatedWithTheCorporateBody 私は日本人です。私は理解していない、そのURI Opaque URIs with human readable labels helps in an international context. Just my two yens worth :) G - Gill Hamilton Digital Access Manager National Library of Scotland George IV Bridge Edinburgh EH1 1EW, Scotland e: g.hamil...@nls.uk t: +44 (0)131 623 3770 Skype: gill.hamilton.nls From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Dan Scott [deni...@gmail.com] Sent: 22 January 2014 21:10 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies Hi Karen: On Wed, Jan 22, 2014 at 3:16 PM, Karen Coyle li...@kcoyle.net wrote: I can't address the first points, but I can speak a bit to the question of meaningful URIs. In the original creation of the RDA elements, meaningful URIs were used based on the actual RDA terminology. This resulted in URIs like: http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequence and... http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequenceManifestation Not only that, the terminology for some elements changed over time, which in some cases meant deprecating a property that was then overly confusing based on its name. Now, I agree that one possibility would have been for the JSC to develop meaningful but reasonably short property names. Another possibility is that we cease looking at URIs and begin to work with labels, since URIs are for machines and labels are for humans. Unfortunately, much RDF software still expects you to work with the underlying URI rather than the human-facing label. We need to get through that stage as quickly as possible, because it's causing us to put effort into URI naming that would be best used for other analysis activities. Thanks for responding on this front. I understand that, while the vocabulary was in heavy active development it might have been painful to adjust as elements changed, but given that this marks the actual publication of the vocabulary, that churn should have settled down, and then this part of the JSC's contribution to semantic web could have semantics applied at both the micro and macro level. I guess I see URIs as roughly parallel to API names; as long as humans are assembling programs, we're likely to benefit from having meaningful (no air quotes required) names... even if sometimes the meaning drifts over time and the code APIs need to be refactored. Dealing with sequentially numbered alphanumeric identifiers reminds me rather painfully of MARC. For what it's worth (and it might not be worth much) curl http://rdaregistry.info/Elements/a/P50101 | grep reg:name | sort | uniq -c shows that the reg:name property is unique across all of the agent properties, at least. Remnants of the earlier naming effort? If that pattern holds, those could have been simply used for the identifiers in place of P#. The most unwieldy of those appears to be otherDesignationAssociatedWithTheCorporateBody (which _is_ unwieldy, certainly, but still more meaningful than http://rdaregistry.info/Elements/a/P50033). Perhaps it's not too late? Follow us on Twitter and Facebook National Library of Scotland, Scottish Charity, No: SCO11086 This communication is intended for the addressee(s) only. If you are not the addressee please inform the sender and delete the email from your system. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of National Library of Scotland. This message is subject to the Data Protection Act 1998 and Freedom of Information (Scotland) Act 2002. No liability is accepted for any harm that may be caused to your systems or data by this message. www.nls.uk
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
Hi Dan, Thanks for taking such an interest! Regarding your questions and concerns: 'slash' vs. 'hash' URIs: As a matter of design, we coin URIs for retrieval of information about the resource identified by the URI by machines, not humans. The most current formal rules[1] state that retrieving a 'slash' fragment should return just that fragment when resolved. We're currently breaking that rule by always returning the entire vocabulary, as if it was indeed using hash URIs and will fix it in the next few weeks. An example of such a fragment (generated by the Open Metadata Registry for http://rdaregistry.info/Elements/w/P10001) is here: http://metadataregistry.org/schemaprop/show/id/15304.rdf We believe, as a matter of good design, that URIs coined for large vocabularies should minimize retrieval bandwidth, particularly since it's highly unlikely that the entire vocabulary will (or should) be retrieved when the properties are used individually as part of an application profile. The entire vocabulary can always be acquired by requesting it from the vocabulary's namespace URI: http://rdaregistry.info/Elements/w/ Lexical (readable, but not semantic) URIs: One of the most common misuses of vocabularies is the misunderstanding of the semantics of the property identified by the URI based on the user's personal, colloquial, or domain-specific interpretation of the semantics of the URI (dc:title is the one I've seem misused most often). So we believe that good vocabulary design _should_ obscure the semantics requiring that the actual vocabulary documentation be viewed by a human. The other problem is that the 'semantics' are most often broadly identified with the lexical label used in the URI. Vocabularies, no matter how stable semantically, _will_ evolve and that evolution often results in a change to the label(s), even if the semantics communicated by the URI don't change. And then there's the issue of spelling (British English vs. American English) and language. Should we assume that the entire world must use, and _understand_ English in order to effectively use a vocabulary? We don't think so. To at least partially address this we have coined multiple URIs for each property, as explained here: http://www.rdaregistry.info/Elements/e/ All RDA URIs have both an immutable canonical form and a 'readable', lexical form, which is subject to change (changes will be redirected). The lexical URIs follow the naming convention you identified and are largely based on the current English (British) label. Content-type: application/octet-stream: We just got the server (nginx) setup yesterday and we haven't yet set the mime types correctly. Again we'll fix that very shortly. Jon Phipps Metadata Management Associates Open Metadata Registry [1] http://www.w3.org/TR/swbp-vocab-pub/ Jon On Wed, Jan 22, 2014 at 12:57 PM, Dan Scott deni...@gmail.com wrote: I'm still pretty new at this linked data thing, but I find it strange that RDA element properties URIs such as http://rdaregistry.info/Elements/a/P50034 and http://rdaregistry.info/Elements/a/P50209 both return the same HTML page in a browser. Would it not have been more usable if the properties used hash-URIs that could have located the particular property on the particular page (e.g. http://rdaregistry.info/Elements/a#P50034)? Also, a plain curl request returns Content-type: application/octet-stream -- but it's pretty clearly Turtle, so I think that should be Content-type: text/turtle I would have liked to see more meaningful URIs--like http://rdaregistry.info/Elements/agent/addressOf instead of http://rdaregistry.info/Elements/a/P50209--as meaningful URIs seem a lot more approachable to this non-machine, but I guess that would have been a lot more work. On Tue, Jan 21, 2014 at 10:45 AM, Diane Hillmann metadata.ma...@gmail.com wrote: Folks: I hope this announcement will be of general interest (and apologies if you receive more than one). Diane -- Forwarded message -- From: JSC Secretary jscsecret...@rdatoolkit.org Date: Tue, Jan 21, 2014 at 10:23 AM Subject: [rules] Publication of the RDA Element Vocabularies snip recipients RDA colleagues, See the announcement below, also posted on the JSC website. Feel free to share this information with your colleagues. Regards, Judy Kuhagen = = = = = The Joint Steering Committee for Development of RDA (JSC), Metadata Management Associates, and ALA Publishing (on behalf of the co-publishers of RDA) are pleased to announce that the RDA elements and relationship designators have been published in the Open Metadata Registry (OMR) as Resource Description Framework (RDF) element sets suitable for linked data and semantic Web applications. The elements include versions unconstrained by Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD), the standard library models
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
On 1/22/14, 3:17 PM, Robert Sanderson wrote: The we might change what this means argument is also problematic -- if you change what it means, then you should change the URI! Otherwise people will continue to use them incorrectly, plus the legacy data generated with the previous definition will suddenly change what it's saying. Rob, absolutely right. If the semantics change, then you need a new property. But labels can change (or more can be added). However, the library world still equates labels with data -- that is, that our data is one-to-one with what we display. That's a huge problem, and it's very hard getting people to think differently about that. I've been looking at the output of the RDA vocabularies over the last couple of days and it IS quite difficult to do so with properties named something like P3058. There is a strong case to be made for mnemonics, although I also take Jon's point that when a property has a name like dc:title it is easy for folks to assume they really know what it means. I would still prefer something memorable at this stage. Finally, 1600 properties... good luck with that. Yes. And remember, RDA was designed to be a *simpler* cataloging code. Can you imagine if it weren't?! kc Rob On Wed, Jan 22, 2014 at 3:03 PM, Hamilton, Gill g.hamil...@nls.uk wrote: Je ne comprends pas l'anglais. Je ne comprends pas l'URI otherDesignationAssociatedWithTheCorporateBody 私は日本人です。私は理解していない、そのURI Opaque URIs with human readable labels helps in an international context. Just my two yens worth :) G - Gill Hamilton Digital Access Manager National Library of Scotland George IV Bridge Edinburgh EH1 1EW, Scotland e: g.hamil...@nls.uk t: +44 (0)131 623 3770 Skype: gill.hamilton.nls From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Dan Scott [deni...@gmail.com] Sent: 22 January 2014 21:10 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies Hi Karen: On Wed, Jan 22, 2014 at 3:16 PM, Karen Coyle li...@kcoyle.net wrote: I can't address the first points, but I can speak a bit to the question of meaningful URIs. In the original creation of the RDA elements, meaningful URIs were used based on the actual RDA terminology. This resulted in URIs like: http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequence and... http://rdvocab.info/Elements/alternativeChronologicalDesignationOfLastIssueOrPartOfSequenceManifestation Not only that, the terminology for some elements changed over time, which in some cases meant deprecating a property that was then overly confusing based on its name. Now, I agree that one possibility would have been for the JSC to develop meaningful but reasonably short property names. Another possibility is that we cease looking at URIs and begin to work with labels, since URIs are for machines and labels are for humans. Unfortunately, much RDF software still expects you to work with the underlying URI rather than the human-facing label. We need to get through that stage as quickly as possible, because it's causing us to put effort into URI naming that would be best used for other analysis activities. Thanks for responding on this front. I understand that, while the vocabulary was in heavy active development it might have been painful to adjust as elements changed, but given that this marks the actual publication of the vocabulary, that churn should have settled down, and then this part of the JSC's contribution to semantic web could have semantics applied at both the micro and macro level. I guess I see URIs as roughly parallel to API names; as long as humans are assembling programs, we're likely to benefit from having meaningful (no air quotes required) names... even if sometimes the meaning drifts over time and the code APIs need to be refactored. Dealing with sequentially numbered alphanumeric identifiers reminds me rather painfully of MARC. For what it's worth (and it might not be worth much) curl http://rdaregistry.info/Elements/a/P50101 | grep reg:name | sort | uniq -c shows that the reg:name property is unique across all of the agent properties, at least. Remnants of the earlier naming effort? If that pattern holds, those could have been simply used for the identifiers in place of P#. The most unwieldy of those appears to be otherDesignationAssociatedWithTheCorporateBody (which _is_ unwieldy, certainly, but still more meaningful than http://rdaregistry.info/Elements/a/P50033). Perhaps it's not too late? Follow us on Twitter and Facebook National Library of Scotland, Scottish Charity, No: SCO11086 This communication is intended for the addressee(s) only. If you are not the addressee please inform the sender and delete the email from your system. The statements and opinions expressed in this
[CODE4LIB] Converting VHS tapes to Digital Files
Greetings, I would like to inquire about possible methods that others have used to convert VHS tapes to digital files. This project would be done in house by library staff. I am familiar with Elgato Video Capture but would like to know about other possible options. Thank you, Jeffrey Sabol
Re: [CODE4LIB] Converting VHS tapes to Digital Files
Composite Capture card (find one on amazon, I use a knock off called EasyCAP) and a VCR (free, I assume you have one): cost about $20 This setup can be used to archive anything with composite out. On the more expensive (faster) side there are solutions where the tape is cut and is run though a machine, but I doubt you want to go that route. These are not the only options, but the best I have come across. //Riley Sent from my iPhone On Jan 22, 2014, at 6:42 PM, Jeffrey Sabol jeffreystephensa...@gmail.com wrote: Greetings, I would like to inquire about possible methods that others have used to convert VHS tapes to digital files. This project would be done in house by library staff. I am familiar with Elgato Video Capture but would like to know about other possible options. Thank you, Jeffrey Sabol
[CODE4LIB] A Job: software developer at GW Libraries
Hi! We're hiring. https://www.gwu.jobs/postings/19740 We are looking for a software developer to join our growing IT team. Our team works on digitization, technology, and development; it comprises full-time staff responsible for digitization operations, IT services, library systems, web development, software development, and project management. We are in the thick of all the things academic library IT groups are doing: improving user experience across diverse services, mass reformatting operations, developing new software and services for our community, and working more and more with diverse data and digital collections. We want to add somebody who will help us move wisely and efficiently through our tasks and projects so we can focus together on redefining the library as a platform for information access and services. Filling this position will double our full-time developer staff. There is room in the position for a healthy range of tasks, roles, starting skill level, and experience (come in at rank L2, L3, or L4) and we can offer an appropriate salary to match. There are good benefits with this Librarian-classed position, including the potential for six months of paid research leave and substantial tuition discounts for employees their family members. And we mean it - right now three members of our team alone (including me) are working on graduate degrees using tuition discounts available to GW employees. Nearly every software project we work on is free and open source; most of our work is managed in github: https://github.com/gwu-libraries We publish our software under an MIT-style license that accords with an explicit free/open source software release policy approved by senior GW administration. We are optimizing our dev workflows around how github works, using tickets, milestones, branches, pull requests, and travis builds. We do this to align ourselves with the broader free software community and because it helps us deliver our work better to the GW community. If this sounds good to you, and if you meet the minimum/basic qualifications, please consider applying. We've got a lot going on and we could use your help. Please get in touch with me if you have any questions. Thanks for reading, -Dan
Re: [CODE4LIB] Converting VHS tapes to Digital Files
This is pretty straightforward to do in real time with a USB breakout cable or device like the Elegato, which I would consider that to be the high end of your effective choices. Pretty much all of the $30-$40 cables are going to get you the same results, and since VHS source quality is such a low bar, you really won't get any benefit from a card or higher end converter. If you want to tweak the video quality, you can do that after the fact. There won't be any benefit from doing it in real-time, which would be relatively expensive. Thanks, Cary On Jan 22, 2014, at 3:41 PM, Jeffrey Sabol jeffreystephensa...@gmail.com wrote: Greetings, I would like to inquire about possible methods that others have used to convert VHS tapes to digital files. This project would be done in house by library staff. I am familiar with Elgato Video Capture but would like to know about other possible options. Thank you, Jeffrey Sabol
Re: [CODE4LIB] Fwd: [rules] Publication of the RDA Element Vocabularies
Hi Karen, On Wed, Jan 22, 2014 at 6:40 PM, Karen Coyle li...@kcoyle.net wrote: I would still prefer something memorable at this stage. The 'lexical', and therefore more memorable, URIs based on the English label will always resolve to the canonical URI. If the lexical label changes, but the semantics don't change, both the old and new lexical URIs will still resolve to the same canonical URI. Of course if both the label and the semantics change, then then it's a new property and gets a new URI. We think that what's urgently needed is a far, far better html representation of the vocabularies: one that makes it obvious that humans can guess mnemonically at a resolvable URI from the label, bearing in mind that this will (hopefully) cause machines (and browsers) to follow the inevitable redirect to the canonical URI. We're actively working on that better representation. Jon
[CODE4LIB] Job: University Librarian at California Institute of Technology
University Librarian California Institute of Technology Pasadena, California, United States, 91125 California Institute of Technology Search for the University Librarian Pasadena, California The California Institute of Technology (Caltech), a world-renowned science and engineering research and teaching university located in Pasadena, California, invites nominations and applications for the position of University Librarian (UL). The successful candidate for this position will be an experienced, forward-thinking library leader who can ensure that Caltech's library fulfills its potential to be an outstanding and accessible resource aligned with the stature of Caltech's faculty and students. Founded in 1891, Caltech is renowned as one of the world's premier universities. U.S. News World Report ranked the Institute as the 10th best university in the United States in their 2013 national rankings. Comprising six primary academic divisions (Biology Biological Engineering; Chemistry Chemical Engineering; Engineering Applied Science; Geological Planetary Sciences; Humanities Social Sciences; and Physics; and Mathematics Astronomy), Caltech enrolls 978 undergraduate students and 1,253 graduate students, with 98% of students placed in the top tenth of their high school graduating class. From its 124-acre campus about 11 miles northeast of downtown Los Angeles, Caltech has made numerous significant contributions toward science; Caltech faculty and alumni have included 32 Nobel Laureates and 57 National Medal of Science Recipients. The Institute manages diverse research programs, including NASA's Jet Propulsion Laboratory (JPL), the Palomar Observatory, and the W. M. Keck Observatory. Caltech stands at an exciting moment, as it will be welcoming its ninth president, Thomas F. Rosenbaum, in July 2014. To learn more about Caltech, see www.caltech.edu. The Caltech library system (the library) comprises five libraries, as well as digital repositories, archives, and special collections. The library is staffed by 22 librarians and other professionals, as well as approximately 11 support staff members and a rotating team of student employees. The library provides an array of services to the campus community, including offering access to academic publications; providing training in academic skills, such as research and grant development; managing computer labs and classrooms; and managing the Caltech Archives, a truly remarkable resource that includes manuscripts, images, oral histories, instruments, and other artifacts chronicling the history of Caltech and the brilliant researchers who have worked there, among them Albert Einstein, Richard Feynman, and Linus Pauling. The University Librarian reports to the Vice Provost of Research at Caltech and serves as a voting member of the faculty. The UL is responsible for all areas of operations across the library system. The UL will work with the library staff - as well as faculty and staff across the Institute - to provide strategic vision and direct day-to-day operations to ensure delivery of consistent, reliable services to the Caltech community. In this role, the UL will be faced with an array of challenges and opportunities. In summary, s/he will: 1) Lead the library staff in developing a compelling vision and strategic plan for an efficient library system that is aligned with Caltech's unique stature as a small but world-class institution, 2) Provide the leadership that unites and empowers library staff to deliver innovative and excellent service; 3) Leverage the library's financial and other resources wisely and pursue additional funding that supports delivery on strategic goals; and 4) Strengthen and expand the library's participation in collaborative relationships with other institutions that provide economies of scale for library resources The successful candidate will be a seasoned administrator with the leadership, managerial, and interpersonal skills to inspire and advocate for library-based programs that provide exceptional service and will have a strong understanding of the core needs of a research-focused academic library in the 21st century. Required qualifications for this role are: *An American Library Association (ALA) accredited Masters of Library Science (MLS), with a secondary Masters or PhD degree desired *A record of sustained scholarly and professional achievement in the field *Significant expertise in the sciences or history of science and an understanding of the research environment *10 years of progressive administrative and managerial academic or research library experience *Demonstrated ability to lead, evaluate and supervise professional level staff *Experience with administering a complex budget with competing demands for funds *Excellent communication and writing skills *Experience in presenting and instructing in individual and group settings *A
Re: [CODE4LIB] [rules] Publication of the RDA Element Vocabularies
Finally, 1600 properties... good luck with that. ROTFL!!! ―ELM
