[CODE4LIB] NOW AVAILABLE: Fifth Alpha Release of Fedora 4
FOR IMMEDIATE RELEASE April 29, 2014 Read it online: http://bit.ly/1koK2tg On the Way to Beta: Fifth Alpha Release of Fedora 4 Winchester, MA The Fedora 4 team is proud to announce the fifth Alpha release of Fedora 4. In the continuing effort to provide rapid access to the quickly growing Fedora 4 feature set, this Alpha release is one of several leading up to the feature-complete Fedora 4 Beta release. Available from the GitHub release[1] * Fedora 4 Alpha 5 One-Click Run [2] * Fedora 4 Alpha 5 web application[3] * Fedora 4 Alpha 5 web application with authorization[4] * Fedora 4 Alpha 5 JMS indexer webapp[5] * Features Versioning This release enhanced the object and datastream versioning capability[6] in two fundamental ways. Specifically, whereas the creation of new versions was previously supported, this release added the logical corollary capability of rolling back to or reverting[7] to a previous version. Also, the deletion[8] of previous versions is now supported. Triplestore While the internal search index within Fedora 4 natively supports the ability to reindex on startup, the recommended pattern[9] for exposing a search experience to repository users did not support the ability to reindex the external Solr or triplestore indices prior to this release. This release introduced an HTTP endpoint[10] for triggering the reindex of external indices for: * the entire repository * a tree of resources within the repository, or * a single repository resource Beyond reindexing, this release also demonstrated the configuration[11] where there are more than one Fedora 4 repositories all feeding events into a single external triplestore. Linked data In the on-going effort to expose repository resources in a standardized, linked-data friendly manner, Fedora 4 continues to keep in step with the maturing Linked Data Platform (LDP) draft specification[12]. Support for appropriate HTTP request headers which allow the user to indicate a preference for the comprehensiveness of triples found in responses was added. Likewise, appropriate HTTP response headers were added that specify paging[13] information and relationships between parent and child resources in an LDP fashion. Performance Tests were performed this release focused on the determination of whether there is an impact on object creation speeds with the increase in the number of child resources (object or datastream) under a single parent resource. These tests were run with multiple backend storage configurations to additionally assess what, if any, factor the storage backend plays into performance trends. Thirty thousand objects (first with 1 KB datastreams, then with 2 MB datastreams) were created at the top level of the repository and individually timed using the following backends: * LevelDB * RAM * File Although a slight up-tick in per object slowdown was indicated during the 2-MB tests, the trend was not absolutely conclusive. Further tests will be repeated with a greater number of objects. The test results can be found on the wiki[14]. Test Coverage Having a comprehensive suite of unit and integration tests affords the Fedora 4 code-base with greater resilience to rippling bugs, demonstrations of expected usage patterns of the APIs and components, as well as enables architectural refactoring to occur with less risk. A focus of this release was to increase our test coverage[15]. The following are the code coverage statistics at the end of this release. * Unit tests: 73.1% * Integration tests: 71.7% * Overall coverage: 86.0% Housekeeping Several feature enhancements and bugs were addressed during this release. Bug fixes and application polishing included: * Added resource locking[16] for concurrent requests on same resource(s) * Locking is available at single node and hierarchy tree levels * Enhanced pluggability of external/internal identifier mappings * Created a utility[17] for uploading a sample dataset to a running Fedora 4 repository * Updated jms-indexer-pluggable integration tests to deploy Fedora webapp in addition to triplestore and indexer webapp * Enhanced REST-API to return timestamp when creating objects and datastreams * Improved HTTP caching headers * Corrected multiple HTTP response codes * Fixed authorization bug which prevented users with both reader and writer roles from reading a resource * Fixed benchtool bug which prevented an equal number of HTTP client threads from being created to support the num threads option References [1] https://github.com/futures/fcrepo4/releases/tag/fcrepo-4.0.0-alpha-5 [2] https://github.com/futures/fcrepo4/releases/download/fcrepo-4.0.0-alpha-5/fcrepo-webapp-4.0.0-alpha-5-jetty-console.war [3]
[CODE4LIB] SubjectsPlus themes
Does anyone have a theme for SubjectsPlus up on github? I'm playing around with the CMS, and I can't find themes. Surely they must exist. -Wilhelmina Randtke
[CODE4LIB] barriers to open metadata?
Hi Code4Libbers, I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. I'm curious about all kinds of barriers: technical, political, financial, cultural. Even if it seems obvious, I'd like to hear about it. Thanks in advance for your feedback! You can send it to me privately if you'd prefer. Laura -- Laura Krier laurapants.comhttp://laurapants.com/?utm_source=email_sigutm_medium=emailutm_campaign=email
Re: [CODE4LIB] SubjectsPlus themes
I searched briefly in the SubjectsPlus group archive but found no mention of themes. https://groups.google.com/forum/?hl=en#!forum/subjectsplus On Tue, Apr 29, 2014 at 11:54 AM, Wilhelmina Randtke rand...@gmail.comwrote: Does anyone have a theme for SubjectsPlus up on github? I'm playing around with the CMS, and I can't find themes. Surely they must exist. -Wilhelmina Randtke
Re: [CODE4LIB] SubjectsPlus themes
I'm not aware of any themes, but you could post to the list. People generally modify the header, footer and css for localization of the front-end. Some sites have customized a lot, but the customizations tend to hew to the parent site's look and feel. Others haven't customized at all, which has led us to rethink the very vanilla default theme. We're just (re)starting a version 3 sprint, but haven't gotten to the front end yet. We're hoping to pretty it up a bit, but I'm not sure we'll have a templating system more than css files to monkey with. If you have suggestions or ideas, please send them to the list, or me, or add as issues in GitHub. Andrew On Tue, Apr 29, 2014 at 1:22 PM, Tom Keays tomke...@gmail.com wrote: I searched briefly in the SubjectsPlus group archive but found no mention of themes. https://groups.google.com/forum/?hl=en#!forum/subjectsplus On Tue, Apr 29, 2014 at 11:54 AM, Wilhelmina Randtke rand...@gmail.com wrote: Does anyone have a theme for SubjectsPlus up on github? I'm playing around with the CMS, and I can't find themes. Surely they must exist. -Wilhelmina Randtke -- Andrew Darby Head, Web Emerging Technologies University of Miami Libraries
[CODE4LIB] Job: Associate Dean for Digital Strategies at University of Miami Libraries
Associate Dean for Digital Strategies University of Miami Libraries Coral Gables, Florida University of Miami Libraries Associate Dean for Digital Strategies Coral Gables, FL The University of Miami Libraries (UML) seeks an Associate Dean to bring vision and innovation to their newly restructured leadership team. The new Associate Dean will join an exceptional team of three other associate deans, supporting the Dean of Libraries, Chuck Eckman. These four individuals will shape and promote the mission of collaboration and develop new programs, structure, and tradition for the University of Miami Libraries. Reporting to the Dean and University Librarian, the Associate Dean for Digital Strategies will provide strategic leadership and direction for the UML digital infrastructure and technology planning. S/he will also provide University-wide leadership and serve as the primary spokesperson for the libraries' digital strategy and services to the UM community, will oversee the Libraries digital production program and infrastructure development for all of the Libraries' digital content management systems and repositories, provide leadership within the Libraries on the creation and curation of digital objects for research and learning, and ensure a robust technical infrastructure to support a wide range of digital scholarship and scholarly publishing. Required qualifications for this role include: • A Master's degree in library and information science, computer science, or a closely related field. • Minimum of five years' experience working in academic research libraries. • Demonstrated knowledge of current trends and issues in the application of technology to libraries and higher education. • Substantive knowledge of digital assets and the technical infrastructure required for their life-cycle management, including metadata requirements, migration strategies, best practices in digital preservation, and relevant national and international standards. • Substantive knowledge of library systems, digital libraries, and digital repositories. • Familiarity with modern software development methodologies and technologies. The University of Miami has retained Isaacson, Miller, a national executive search firm, to assist in this recruitment. All applications, inquiries, and nominations should be submitted in confidence via Isaacson, Miller's website at www.imsearch.com/5095. Inquiries should be directed to Beverly Brady, Senior Associate, and Julie Yermack, Associate. Please visit https://library.miami.edu/ for additional information. The University of Miami offers competitive salaries and a comprehensive benefits package including medical and dental benefits, tuition remission, vacation, paid holidays and much more. The University of Miami is an Equal Opportunity/Affirmative Action Employer. [Apply Here](http://www.Click2Apply.net/wsby3pb) Brought to you by code4lib jobs: http://jobs.code4lib.org/job/14071/
Re: [CODE4LIB] barriers to open metadata?
Hi, On Tue, Apr 29, 2014 at 10:02 AM, Laura Krier laura.kr...@gmail.com wrote: I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. I'm curious about all kinds of barriers: technical, political, financial, cultural. Even if it seems obvious, I'd like to hear about it. Here's one technical barrier: there are some ILSs that don't respond well to web crawlers; in particular, although GoogleBot tends to crawl at a reasonable rate, there are other badly behaved ones (AhrefsBot, I'm looking at you!) that can effectively perform a denial-of-service attack on a library catalog. Of course, there are a number of ways to mitigate such issues and allow crawling, However, given the choice between allowing crawlers (for purposes that don't necessary have immediate benefit to the library) and maintaining uptime for the human users, often the convenient decision is to block the bots. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
Re: [CODE4LIB] barriers to open metadata?
Hi Laura, Here are some reasons I may have overheard. Stuck halfway: We have an OAI-PMH endpoint, so we're open, right? Lack of funding for sorting out our own rights: We gathered metadata from various sources and integrated the result - we even call ourselves Open L*y - but we [don't have manpower to figure out what we can do with it, so we added a disclaimer]. Cultural: We're not sure how to prevent losing the records' provenance after we released our metadata. Groeten van Ben On 29-04-14 19:02, Laura Krier laura.kr...@gmail.com wrote: Hi Code4Libbers, I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. I'm curious about all kinds of barriers: technical, political, financial, cultural. Even if it seems obvious, I'd like to hear about it. Thanks in advance for your feedback! You can send it to me privately if you'd prefer. Laura -- Laura Krier laurapants.comhttp://laurapants.com/?utm_source=email_sigutm_medium=emai lutm_campaign=email
Re: [CODE4LIB] barriers to open metadata?
Hi Laura I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. One issue is that we pay for enrichments (tables of contents etc) for records, and I believe the licence restricts us from giving them to other people. We send our records to the national union catalogue and OCLC before adding the enrichments, and we'd need to take them out before we could release records elsewhere. Cheers David
Re: [CODE4LIB] barriers to open metadata?
On 04/30/2014 09:38 AM, David Friggens wrote: Hi Laura I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. One issue is that we pay for enrichments (tables of contents etc) for records, and I believe the licence restricts us from giving them to other people. We send our records to the national union catalogue and OCLC before adding the enrichments, and we'd need to take them out before we could release records elsewhere. Note that this is primarily a problem because MARC assumes that all versioning is done at the record level; there's no easy way to say the core bib item is from X, the TOC is from Y and the cover image is from Z. cheers stuart
Re: [CODE4LIB] barriers to open metadata?
On Tue, Apr 29, 2014 at 1:02 PM, Laura Krier laura.kr...@gmail.com wrote: Hi Code4Libbers, I'd like to find out from as many people as are interested what barriers you feel exist right now to you releasing your library's bibliographic metadata openly. I'm curious about all kinds of barriers: technical, political, financial, cultural. Even if it seems obvious, I'd like to hear about it. In the field (hah) of MARC records, some vendors charge for MARC as a value-add on top of the electronic resources they provide. Here's one I could think of off the top of my head: http://gdc.gale.com/products/eighteenth-century-collections-online/acquire/marc-records/ So as soon as you start mixing records that you've purchased (presumably under a license that restricts redistribution) into an otherwise open set of metadata, you're in a world of pain... because typically systems are binary (either they make all of the bibliographic metadata openly available, or none of it). Of course this means that many sites are probably serving up these sorts of records via SRU or Z39.50 when they really should not be. But it certainly gives pause to sites that might otherwise package up one-time or monthly dumps of all of their data. I suspect there are also lingering effects of OCLC's aborted attempt to place restrictions on the transfer of records from WorldCat back in 2008 [1, 2]. This has now instead become a reasonable recommendation concerning ODC-BY licensing [3] but the confusion and uncertainty about which records an OCLC member may redistribute remains. 1. https://web.archive.org/web/20130925190859/http://blog.reeset.net/archives/574 2. https://coffeecode.net/archives/174-Archive-of-OCLC-WorldCat-Policy-as-posted-2008-11-02.html 3. http://www.oclc.org/news/releases/2012/201248.en.html Dan
Re: [CODE4LIB] barriers to open metadata?
This has now instead become a reasonable recommendation concerning ODC-BY licensing [3] but the confusion and uncertainty about which records an OCLC member may redistribute remains. [3] http://www.oclc.org/news/releases/2012/201248.en.html Allow me to try to put this confusion and uncertainty to rest once and for all: ALL THE THINGS. ALL. At least as far as we are concerned. I think it's well past time to put the past in the past. Meanwhile, we have just put nearly 200 million works records up as linked open data. [1], [2], [3]. If that doesn't rock the library open linked data world, then no one is paying attention. Roy [1] http://oclc.org/en-US/news/releases/2014/201414dublin.html [2] http://dataliberate.com/2014/04/worldcat-works-197-million-nuggets-of-linked-data/ [3] http://hangingtogether.org/?p=3811
