DigitalKoans

Jon Udell's wide-ranging Perspectives interview with Tony Hey, Corporate Vice President of Microsoft’s External Research Division, is now available.

The DSpace Foundation has published the July/August NewSpace newsletter.

Fedora Commons has released version 3.0 Fedora, which "completes all general release features."

Here's an excerpt from the press release:

Dan Davis, Chief Software Architect, Fedora Commons, explained, "We are pleased to offer a Fedora 3.0 that is a foundational step towards a model-driven content architecture." He went on to say, "Users will find it simpler to maintain and operate their repositories with version 3.0-it's more scalable and fits better into the Web."

Fedora 3.0 features the Content Model Architecture (CMA), an integrated structure for persisting and delivering the essential characteristics of digital objects in Fedora. The software is available at http://www.fedora-commons.org/ and at http://sourceforge.net/projects/fedora-commons. The Fedora CMA plays a central role in the Fedora architecture, in many ways forms the over-arching conceptual framework for future development of Fedora Repositories. Fedora 3.0 features include:

Overview of new Features in Fedora 3.0 Release

• Content Model Architecture—Provides a model-driven approach for persisting and delivering the essential characteristics of digital content in Fedora
• Fedora REST API—A new API that exposes a subset of the Access and Management API using a RESTful Web interface contributed by MediaShelf
• Mulgara Support—Fedora supports the Mulgara 2.0 Semantic Triplestore replacing Kowari
• Migration Utility—Provides an update utility to convert existing collections for Content Model Architecture compatibility
• Relational Index Simplification—The Fedora schema was simplified making changes easier without having to reload the database and significantly increasing scalability
• Dynamic Behaviors—Objects may be added or removed dynamically from the system moving system checks into run-time errors
• Error Reporting—Provides improved run-time error details
• Multiple Owner as a CSV String—Enables using a CSV string as ownerID and in XACML policies
• Java 6 Compatibility—Fedora may be optionally compiled using Java 6 while retaining support for Java Enterprise Edition 1.5 deployments
• Relationships API—API-M has been extended to enable adding, removing, and discovering RDF relations between Fedora objects
• Revised Fedora Object XML Schemas—The new schemas are simpler, supporting the CMA and removing Disseminators
• Atom Support—Fedora objects can now be imported and exported in the Atom format
• Messaging Support—Integrates JMS messaging for sending notification of important events
• Validation Framework—Provides system operators a way to validate all or part of their repository, based on content models
• 3.0-Compatible Service Releases—New versions of the OAI Provider and GSearch services are compatible with Fedora 3.0. The GSearch release also enables messaging support for GSearch, which allows for more robust and seamless integration with the Fedora repository.
• Many new enhancements—see the Release Notes:
  http://www.fedora-commons.org/documentation/3.0b2/
  userdocs/distribution/release-notes.html.

OCLC has announced the availability of Web Harvester, which allows CONTENTdm sites to import Web content into their systems.

Here's an excerpt from the press release:

OCLC's Web Harvester evolved from collaboration with several state libraries, state archives and universities over a period of seven years. Participants emphasized the increasing importance of collecting and managing Web-based content as information resources move online yet remain within libraries' and archives' collection scopes.

The Web Harvester is integrated into library workflows, allowing library staff to capture content as part of the cataloging process. The captured content is then sent to the organization's digital collections where it can be managed with other CONTENTdm digital content. . . .

The Web Harvester is accessed via the Connexion client, OCLC's powerful cataloging service, and captures content ranging from single, Web-based documents to entire Web sites. Once retrieved, users can review the captured Web content and add it to a collection managed by OCLC's CONTENTdm software, a complete solution for storing, managing and delivering a library's digital collections to the Web. Once in CONTENTdm, then Web content can be accessed and managed in conjunction with other digital collections. Harvested items are discoverable from WorldCat.org, WorldCat Local and the CONTENTdm Web interface.

For additional security, master files of the captured content also can be ingested to the OCLC Digital Archive, the service for long-term storage of originals and master files from libraries' digital collections.

OpenDOAR is mapping repository data using Google Maps.

Here's an excerpt from the announcement:

SHERPA is pleased to announce the addition of a Google Maps extension to OpenDOAR, its directory of open access repositories (http://www.opendoar.org/find). Just run any search of the directory, and then change the output format from "Summaries" to "Google Map".

Here are a few examples:

1. http://www.opendoar.org/find?format=gmap&cID=jp
—Repositories in Japan . . .

3. http://www.opendoar.org/find?format=gmap&cID=us&ctID=6
—United States repositories holding theses & dissertations

4. http://www.opendoar.org/find?format=gmap&search=Nottingham
—Keyword search for "Nottingham"

5. http://www.opendoar.org/find?format=gmap&rSoftWareName=
CONTENTdm
—Repositories using CONTENTdm software

The DSpace Foundation and Fedora Commons have announced that they will collaborate on future digital repository initiatives.

Here's an excerpt from the press release:

Today two of the largest providers of open source software for managing and providing access to digital content, the DSpace Foundation and Fedora Commons, announced plans to combine strengths to work on joint initiatives that will more closely align their organizations' goals and better serve both open source repository communities in the coming months. . . .

The collaboration is expected to benefit over 500 organizations from around the world who are currently using either DSpace (examples include MIT, Rice University, Texas Digital Library and University of Toronto) or Fedora (examples include the National Library of France, New York Public Library, Encyclopedia of Chicago and eSciDoc) open source software to create repositories for a wide variety of purposes. . . .

The decision to collaborate came out of meetings held this spring where members of DSpace and Fedora Commons communities discussed multiple dimensions of cooperation and collaboration between the two organizations. Ideas included leveraging the power and reach of open source knowledge communities by using the same services and standards in the future. The organizations will also explore opportunities to provide new capabilities for accessing and preserving digital content, developing common web services, and enabling interoperability across repositories.

In the spirit of advancing open source software, Fedora Commons and DSpace will look at ways to leverage and incubate ideas, community and culture to:

1. Provide the best technology and services to open source repository framework communities.
2. Evaluate and synchronize, where possible, both organizations' technology roadmaps to enable convergence and interoperability of key architectural components.
3. Demonstrate how the DSpace and Fedora open source repository frameworks offer a unique value proposition compared to proprietary solutions.

The announcement came on the heels of an event sponsored by the Joint Information Systems Committee's (JISC) Common Repository Interface Group (CRIG) held at the Library of Congress. The event, known as "RepoCamp," was a forum where developers gathered to discuss innovative approaches to improving interoperability and web-orientation for digital repositories. Sandy Payette, Executive Director of Fedora Commons, and Michele Kimpton, Executive Director of the DSpace Foundation, reiterated their commitment to collaboration and encouraged input and participation from both communities as work gets underway.

The Oxford University Office of the Director of IT has released Findings of the Scoping Study Interviews and the Research Data Management Workshop: Scoping Digital Repository Services for Research Data Management.

Here's an excerpt from the report's Web page:

The scoping study interviews aimed to document data management practices from Oxford researchers as well as to capture their requirements for services to help them manage their data more effectively. In order to do this, 37 face-to-face interviews were conducted between May and June with researchers from 27 colleges, departments and faculties. In addition to this, the Research Data Management Workshop was organised to complement the findings of the scoping study interviews.

The Australian Partnership for Sustainable Repositories has released Investigating Data Management Practices in Australian Universities.

Here an excerpt from the report's Web page:

In late 2007, The University of Queensland undertook a survey of data management practices among the university’s researchers. This was done in response to the increasing realisation that repositories need to include research data, in addition to the research outputs in print form already included, and to provide information which would enhance the support provided for those engaged in eResearch.

The survey was carried out using the Apollo software developed at The Australian National University and adapted by APSR. Two other universities, The University of Melbourne and the Queensland University of Technology, have now replicated the survey among their own communities, while adding some questions of local interest.

The survey covers questions such as the types of digital data being created (spreadsheets, documents, experimental data, images, fieldwork data, etc), the size of the data collection, software used for data analysis, data storage and backup, application of a data management plan, roles and responsibilities around data management, copyright frameworks, usage of high capacity computing, and much more.