DSpace

Winchester, MA  The Fedora team has concluded the twelfth sprint within the "Beta Phase" of Fedora4 development. The work of this and each sprint is planned and completed thanks to the contributions of Fedora stakeholder institutions which allocate ... [More] developer time. If you would like to be involved with Fedora4 development, please send an email to Andrew Woods [email protected], or to [email protected]. If you have comments on the work from this sprint, please also send an email or comment directly on the wiki. Read the the Sprint B12 summary: https://wiki.duraspace.org/display/FF/Sprint+B12+Summary About Sprint 12, Beta Phase Development Team Frank Asseg - FIZ Karlsruhe Adam Soroka - University of Virginia Greg Jansen - University of North Carolina, Chapel Hill Ben Pennell - University of North Carolina, Chapel Hill Mike Daines - University of North Carolina, Chapel Hill Sprint Themes 1) Clustering Incremental progress continues to be made towards the Fedora 4 clustering [1] capability. A set of Fedora Puppet scripts [2] have been refined which enable consistent clustering. In addition to the scripts and configuration details themselves, several tips and gotchas related to cluster deployment are included in the linked resources. 2) Authorization In order to address the breadth of Authorization use cases [3], this sprint enhanced the Fedora 4 Authorization framework for two fundamental purposes: - Enable the full context of servlet requests to be available to the Authorization enforcement point, and - Make the Authorization interface boundaries abstract enough to allow both HTTP as well as embedded Java client requests to leverage the same security infrastructure. Use case specific implementations are still required, but the framework should be flexible enough to now support a variety of scenarios including the integration of LDAP, filtering on request I.P. address, and restricting access by license-based policies. 3) Performance - Single Node The improvement of Fedora 4's performance (in the form of user response-time) is a continual priority. In the "Holiday Release", Alpha-3, we compared the results [4] of ingest events against Fedora 3 and Fedora 4 installations. It has since been determined that one of the greatest impacts on response-time comes from the "persist" or "commit" phase of a repository interaction. Given that, this sprint retooled thebenchmarking utility [5] to optionally wrap performance tests within transactions. What the transaction offers is the ability to consolidate a set of repository updates into a single "commit" versus "committing" after every request. The results [6] of executing suites of delete, ingest, and update operations with and without transactions reveal the following improvements: - Delete: 62% improvement - Ingest: 33% improvement - Update: 32% improvement 4) Test Coverage Unit and Integration test coverage [7] is a vital factor in maintaining a healthy code base. The following are the code coverage statistics at the end of this sprint, and the change from the previous sprint. - Unit tests: 71.3% (up 6.8%) - Integration tests: 71.1% (down 0.3%) - Overall coverage: 84.4% (up 0.6%) 5) Housekeeping Several bugs were addressed during this sprint. Bug fixes and application polishing included: - Optionally caching checksums of content under filesystem projection - Consolidating previously scattered configuration files into a single package - Refactoring additional kernel interfaces from implementation classes - Removing dead code References [1] https://wiki.duraspace.org/display/FF/Deploying+a+Fedora+Cluster [2] https://github.com/futures/puppet-fcrepo/blob/master/README.md [3] https://wiki.duraspace.org/label/FF/uc-authz [4] https://wiki.duraspace.org/display/FF/Single-Node+Test+Results#Single-NodeTestResults-Fedora3/4Comparison [5] https://github.com/futures/benchtool [6] https://wiki.duraspace.org/display/FF/Single-Node+Test+Results#Single-NodeTestResults-TransactionalversusNon-transactionalTestsResults%28Benchtool%29 [7] http://sonar.fcrepo.org/dashboard/index/1 [Less]

“DSpaceDirect Details” is an ongoing series of blog posts relating key features of the only low-cost hosted repository solution for discovery, access, and archiving to common institutional repository issues Winchester, MA  Once the decision is ... [More] made, when is the best time to launch your institutional repository? How about right away? DSpaceDirect puts you in control of the timing. The strategic choice to boost visibility by inviting the world in through an open access repository is often followed by implementation questions. Most organizations want to make an early version of their repository available rapidly as they move towards planning for a public launch of their IR. Oceana Wilson, Director of Library and Information Services Crossett Library, Bennington College explains, "For us, a small liberal arts college, DSpaceDirect offered a triple opportunity: a solution for establishing a digital repository and an archive delivered in a true turnkey, all tech support provided package with extremely competitive pricing as a bonus. We were up and running right away. It has been a really great experience." Read more about the Bennington College Crossett Library DSpaceDirect repository here. DSpaceDirect makes the first step easy. You don't need local servers or system administrators to get started because the DSpaceDirect team walks you through the repository quick-start process and manages the software installation, maintenance, and servers. You keep costs low while having more time to concentrate on developing a repository management workflow, establishing criteria for content, eliciting materials and seeing how search and browse operate in the user interface. The sooner an IR is available for faculty, staff, students and the general public to interact with, the sooner others have the ability to find previously hidden open access institutional resources. ABOUT DSPACE DIRECT DSpaceDirect is the only hosted repository solution for low-cost discovery, access, archiving, and preservation from DuraSpace (http://duraspace.org), an independent 501(c)(3) not-for-profit organization. DSpaceDirect is available with convenient features that include fast start-up, you-pick customization, no-cost upgrades, content preservation options, anytime data access and all-the-time data control–all at a price that puts solutions for long-term access to digital scholarly assets within reach of institutions of any size. • More about DSpaceDirect: http://dspacedirect.org/benefits • DSpaceDirect prices: http://dspacedirect.org/pricing • Get a DSpaceDirect quote right away: http://dspacedirect.org/inquiry [Less]

“DSpaceDirect Details” is an ongoing series of blog posts relating key features of the only low-cost hosted repository solution for discovery, access, and archiving to common institutional repository issues Winchester, MA  Once the decision is ... [More] made, when is the best time to launch your institutional repository? How about right away? DSpaceDirect puts you in control of the timing. The strategic choice to boost visibility by inviting the world in through an open access repository is often followed by implementation questions. Most organizations want to make an early version of their repository available rapidly as they move towards planning for a public launch of their IR. Oceana Wilson, Director of Library and Information Services Crossett Library, Bennington College explains, "For us, a small liberal arts college, DSpaceDirect offered a triple opportunity: a solution for establishing a digital repository and an archive delivered in a true turnkey, all tech support provided package with extremely competitive pricing as a bonus. We were up and running right away. It has been a really great experience." Read more about the Bennington College Crossett Library DSpaceDirect repository here. DSpaceDirect makes the first step easy. You don't need local servers or system administrators to get started because the DSpaceDirect team walks you through the repository quick-start process and manages the software installation, maintenance, and servers. You keep costs low while having more time to concentrate on developing a repository management workflow, establishing criteria for content, eliciting materials and seeing how search and browse operate in the user interface. The sooner an IR is available for faculty, staff, students and the general public to interact with, the sooner others have the ability to find previously hidden open access institutional resources. ABOUT DSPACE DIRECT DSpaceDirect is the only hosted repository solution for low-cost discovery, access, archiving, and preservation from DuraSpace (http://duraspace.org), an independent 501(c)(3) not-for-profit organization. DSpaceDirect is available with convenient features that include fast start-up, you-pick customization, no-cost upgrades, content preservation options, anytime data access and all-the-time data control–all at a price that puts solutions for long-term access to digital scholarly assets within reach of institutions of any size. • More about DSpaceDirect: http://dspacedirect.org/benefits • DSpaceDirect prices: http://dspacedirect.org/pricing • Get a DSpaceDirect quote right away: http://dspacedirect.org/inquiry [Less]

From Susan Manus, Library of Congress/NDIIPP Washington, DC  The March, 2014 issue of the Library of Congress Digital Preservation Newsletter is now available: http://www.digitalpreservation.gov/news/newsletter/201403.pdf. Included in this issue: ... [More] • A Career's Worth of Archives - Bill LeFurgy talks about his career and personal archives, as he heads into retirement • New NDSA Report:  PDF/A-3 for Archival Institutions • CFP for Digital Preservation 2014 - deadline is March 14th • What Do You Mean by "Archive"?  Genres of Usage for Digital Preservers • An Interview with public radio's John Passmore • Upcoming events:  DERCOMP Digital Curation, Computers in Libraries, Texas Library Association, Personal Digital Archiving 2014, 2014 Midwest Archives Conference • Recent articles about the NDSA, web archiving, residency program and much more. [Less]

A message from the Open Repositories 2014 Conference organizers Helsinki, Finland  Sponsorship opportunities are now available for the International Conference on Open Repositories (OR2014). The event will take place from Monday 9 June to Friday 13 ... [More] June 2014 in Helsinki, Finland. Is your organisation a market leader in digital asset management, digital storage, research information systems or scholarly communication? If so OR2014 is a great occasion to showcase products and services and to communicate your brand to leaders and decision makers in the open repository community. Your company or organization can demonstrate active involvement in the global effort toward interoperable open repositories that provide broad access to quality information and resources. Details regarding sponsorship opportunities options can be found on the conference web site: http://or2014.helsinki.fi/?page_id=375. You can also contact [email protected] for further information and reservation of sponsorships. [Less]

Winchester, MA  The Fedora team has concluded the eleventh sprint within the "Beta Phase" of Fedora4 development. The work of this and each sprint is planned and completed thanks to the contributions of Fedora stakeholder institutions which allocate ... [More] developer time. If you would like to be involved with Fedora4 development, please send an email to Andrew Woods [email protected], or to [email protected]. If you have comments on the work from this sprint, please also send an email or comment directly on the wiki. Read the the Sprint B11 summary: https://wiki.duraspace.org/display/FF/Sprint+B11+Summary About Sprint 11, Beta Phase Development Team Frank Asseg - FIZ Karlsruhe Adam Soroka - University of Virginia Michael Durbin - University of Virginia Scott Prater - University of Wisconsin Greg Jansen - University of North Carolina, Chapel Hill Ben Pennell - University of North Carolina, Chapel Hill Mike Daines - University of North Carolina, Chapel Hill Osman Din - Yale University Eric James - Yale University Sprint Themes 1) Clustering The clustering feature of Fedora 4 holds the promise to address a range of use cases from horizontal load-scaling, to high availability, to geographic distribution. The short-term goal is to demonstrate a proportional increase in performance with the addition of cluster nodes for load-intensive operations such as object creation. Previous work has focused on the simple establishment of multi-node clusters along with configuration experiments towards optimizing object creation. This sprint furthered the effort by establishing Fedora 4 clusters [1] at two additional institutions. While the focus is on determining which underlying ModeShape and Infinispan configurations optimize stakeholder use cases, a parallel effort was put towards developing repeatable, scripted Puppet deployments. 2) Transactions Transactions [2] are important not only for bounding a set of repository interactions into a single, atomic unit, but also for their performance benefits. Much of the time in a user request goes towards the saving or commit of the action's update(s) to the repository. Transactions offer the potential of grouping a set of interactions, and their associated persistence events, into a single commit. A bug which prevented transactions across different HTTP sessions was fixed during this sprint through a community contribution (Kai Strnad). Further profiling of the exact performance benefits of transactions on a variety of actions (creation, update, deletion) is outstanding. 3) Versioning The Alpha-3 implementation of versioning [3] exposed previous versions of a repository resource in the case where no authorization was configured on the repository. This sprint extends the basic functionality by exposing versions to users that have read access to the resource, if authorization is enable. 4) Pluggable Framework As of the Alpha-3 release, Fedora 4 has been demonstrably "easy" to install/deploy. Work during this sprint was put into the design and prototyping of a wiring and pluggability framework that would additionally make the runtime configuration of Fedora 4 "easy". 5) 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 sprint was to increase our test coverage [4]. The sprint started with 64.5% unit and 71.4% integration 83.8% total test coverage. The sprint ended with 71.3% , 71.1%, and 84.4%, respectively. 6) Housekeeping Several bugs were addressed during this sprint along with the addition of tests that provoke the would-be bug scenarios. Bug fixes and application polishing included: • Catching errors when submitting an empty admin search query • Creating an "authorization-enabled" deployable war file on the default build • Upgrading the underlying ModeShape version to 3.7.1 • Exposing primary types, mixin-types and each of their ancestor hierarchies in responses, which enables indexing to be aware of resource super-types • Creating resources on a PUT request if it does not exist • Consolidation of previously dispersed configuration files • Correcting the syntax of the LDP "Link" header, as surfaced through community input • Addition of authorization unit tests 7) Developer Capacity For the short and long-term health of Fedora development, the committer base must continue to expand. This sprint witnessed the addition of two new developers from the University of North Carolina, Chapel Hill. References [1] https://wiki.duraspace.org/display/FF/Clustering [2] https://wiki.duraspace.org/display/FF/Transactions [3] https://wiki.duraspace.org/display/FF/Versioning [4] http://sonar.fcrepo.org/dashboard/index/1 [Less]

From Mark Wood, Lead System Programmer, IUPUI, on behalf of the DSpace 4.1 Release Team, and all the DSpace developers DSpace developers have announced that that DSpace 4.1 is now available!  DSpace 4.1 is a bug-fix release to the recent release of ... [More] feature-rich DSpace 4.0 which includes tools for improving your users’ experience and web services integrations. DSpace 4.1 contains no new features. Download DSpace 4.1 immediately at either of the following locations: • SourceForge: https://sourceforge.net/projects/dspace/files/ • GitHub: https://github.com/DSpace/DSpace/ (see the "dspace-4.1" tag) In addition, you are welcome to try out DSpace 4.1 on http://demo.dspace.org/ and continue to provide any early feedback you may have. Fixed in 4.1 • Fixed issue where having a period (.) in your handle prefix     generated incorrect identifiers (DS-1536) • Fixed broken quick build (from [dspace-src]/dspace) (DS-1867) • Fixed a crash of DSpace during CSV import via BTE (DS-1857) • Fixed collection harvesting to DSpace via ORE (DS-1848) • Fixed deposit of new items via SWORD (DS-1846) • Fixed search hit highlighting in XMLUI (DS-1907) • Fixed broken 'stat-initial' script (DS-1795) • Other minor fixes. See Changes in 4.x section for a list of all fixes. For much more information on each of these features, please visit our 4.x Release Notes: https://wiki.duraspace.org/display/DSDOC4x/Release+Notes 4.1 Documentation The DSpace 4.x documentation is available online at: https://wiki.duraspace.org/display/DSDOC4x/ A PDF copy of the documentation is still distributed with the software. In addition, it can also be downloaded from: http://www.dspace.org/latest-release/ 4.1 Acknowledgments The DSpace application would not exist without the hard work and support of the community. Thank you to the many developers who have worked very hard to deliver all the new features and improvements. Also thanks to the users who provided input and feedback on the development, as well those who participated in the testathons. Additionally I would like to thank Tim Donohue of DuraSpace for ensuring that DSpace 4.1 went off without a hitch. A detailed listing of all known people/institutions who contributed directly to DSpace 4.1 is available in the Release Notes.  If you contributed and were accidentally not listed, please let us know so that we can correct it! For DSpace 4.1 a total of 25 individuals contributed bug reports and bug fixes.  A big thanks goes out to everyone who participated.  We hope you'll continue to be a valuable addition to the DSpace community for the next release and beyond! More Information More information on this release is available in the DSpace 4.1 Release Notes: https://wiki.duraspace.org/display/DSDOC4x/Release+Notes As always, we look forward to hearing from the community about DSpace. Please let us know what you think of 4.1! [Less]

From Mark Wood, Lead System Programmer, IUPUI, on behalf of the DSpace 4.1 Release Team, and all the DSpace developers DSpace developers have announced that that DSpace 4.1 is now available!  DSpace 4.1 is a bug-fix release to the recent release of ... [More] feature-rich DSpace 4.0 which includes tools for improving your users’ experience and web services integrations. DSpace 4.1 contains no new features. Download DSpace 4.1 immediately at either of the following locations: • SourceForge: https://sourceforge.net/projects/dspace/files/ • GitHub: https://github.com/DSpace/DSpace/ (see the "dspace-4.1" tag) In addition, you are welcome to try out DSpace 4.1 on http://demo.dspace.org/ and continue to provide any early feedback you may have. Fixed in 4.1 • Fixed issue where having a period (.) in your handle prefix     generated incorrect identifiers (DS-1536) • Fixed broken quick build (from [dspace-src]/dspace) (DS-1867) • Fixed a crash of DSpace during CSV import via BTE (DS-1857) • Fixed collection harvesting to DSpace via ORE (DS-1848) • Fixed deposit of new items via SWORD (DS-1846) • Fixed search hit highlighting in XMLUI (DS-1907) • Fixed broken 'stat-initial' script (DS-1795) • Other minor fixes. See Changes in 4.x section for a list of all fixes. For much more information on each of these features, please visit our 4.x Release Notes: https://wiki.duraspace.org/display/DSDOC4x/Release+Notes 4.1 Documentation The DSpace 4.x documentation is available online at: https://wiki.duraspace.org/display/DSDOC4x/ A PDF copy of the documentation is still distributed with the software. In addition, it can also be downloaded from: http://www.dspace.org/latest-release/ 4.1 Acknowledgments The DSpace application would not exist without the hard work and support of the community. Thank you to the many developers who have worked very hard to deliver all the new features and improvements. Also thanks to the users who provided input and feedback on the development, as well those who participated in the testathons. Additionally I would like to thank Tim Donohue of DuraSpace for ensuring that DSpace 4.1 went off without a hitch. A detailed listing of all known people/institutions who contributed directly to DSpace 4.1 is available in the Release Notes.  If you contributed and were accidentally not listed, please let us know so that we can correct it! For DSpace 4.1 a total of 25 individuals contributed bug reports and bug fixes.  A big thanks goes out to everyone who participated.  We hope you'll continue to be a valuable addition to the DSpace community for the next release and beyond! More Information More information on this release is available in the DSpace 4.1 Release Notes: https://wiki.duraspace.org/display/DSDOC4x/Release+Notes As always, we look forward to hearing from the community about DSpace. Please let us know what you think of 4.1! [Less]

Cochin, India  A two-day workshop focused on DSpace open source software for building digital repositorie and libraries will be held at Cochin University of Science and Technology located in Cochin, Kerala, India March 22-23, 2014. "DSpace ... [More] incorporates a digital asset management system and helps to create, index and retrieve various forms of digital contents. DSpace is adaptable to various needs of Libraries and Information Centres and maintains built-in interoperability programs for application between various systems. It adheres to international standards for metadata." For more details visit http://soe.cusat.ac.in/cs/dspaceworkshop/ [Less]

Cochin, India  A two-day workshop focused on DSpace open source software for building digital repositorie and libraries will be held at Cochin University of Science and Technology located in Cochin, Kerala, India March 22-23, 2014. "DSpace ... [More] incorporates a digital asset management system and helps to create, index and retrieve various forms of digital contents. DSpace is adaptable to various needs of Libraries and Information Centres and maintains built-in interoperability programs for application between various systems. It adheres to international standards for metadata." For more details visit http://soe.cusat.ac.in/cs/dspaceworkshop/ [Less]