BieColl - Bielefeld Electronic Collections
Not a member yet
1004 research outputs found
Sort by
DSpace 1.6 usage statistics: What it can do for you?
Get PDFIntroduction
DSpace 1.6 has been extended with a new Apache Solr based statistics solution. This contribution to DSpace is the open-source version of @mire's commercial "Content and Usage Analysis" DSpace module. The DSpace 1.6 statistics offer storage of usage data including bitstream downloads, item display page visits, collection and community homepage visits, ...
DSpace Discovery: Unifying DSpace Search and Browse with Solr
Get PDFOne key innovation long awaited by the DSpace community is a more intuitive and unified search and browse experience. NESCent and @mire NV have collaborated to create a new Faceted Search and Browse experience for NESCent's DSpace repository, Dryad. DSpace Discovery is a modular Add-on for DSpace XMLUI that replaces DSpace search and browse with Solr. The implementation of Discovery's Services utilize the DSpace Services API originally developed for DSpace 2.0 and back-ported for use within the recent release of DSpace 1.6.0. Thus, DSpace Discovery represents the next stage in @mire's DSpace 2.0 development initiative
From Dynamic to Static: the challenge of depositing, archiving and publishing constantly changing content from the information environment
Get PDFA repository used for storing and disseminating research is a canonical example of a system which strives to produce stable artefacts which can be reliably referenced, if not actually reserved, over time. This is a difficult task, since the normal state of information is constant flux: being updated, revised, rewritten, removed and republished. Recent work in deposit technology has tended to centre around the use of a repository as a 'final resting place' for some research item. It has typically used packages of content, roughly analogous to the SIP (Submission Information Package) in OAIS (http://public.ccsds.org/publications/archive/650x0b1.pdf), to insert 'finished' works into the archive. An example of this is SWORD (http://www.swordapp.org/), which addresses in great detail the deposit mechanism, but is largely reliant on the payload being a single file (for example, a zip), containing all the information that the repository needs in order to create an archival object. This places a burden on the depositor to make an assertion that an item is finished and ready for archiving, and pushes tasks that the repository is traditionally good at (i.e. storing content) out to whatever system the user is creating their work in. Over the past year, Symplectic Ltd (http://www.symplectic.co.uk/) has attempted to break down this reliance on the "package", and move repository deposit in the direction of not only full CRUD (Create, Retrieve, Update, Delete), but also to give repository workflows the opportunity to define when a work is "finished" (at least, provisionally). This will give the repository the opportunity to do what it does best (i.e. store content), and to allow the administrators - experts in repositories and archiving - to have a hand in determining whether an item is "finished", relieving these burdens from the depositor and their research process
On Constructing Repository Infrastructures: The D-NET Software Toolkit
Get PDFDue to the wide diffusion of digital repositories, organizations responsible for large research communities, such as national or project consortia, research institutions, foundations, are increasingly tempted into setting up so-called repository infrastructure systems (e.g., OAIster (http://www.oaister.org), BASE (http://www.base-search.net), DAREnet-NARCIS (http://www.narcis.info)). Such systems offer web portals, services and APIs for cross-operating over the metadata records of publications (lately also of experimental data and compound objects) aggregated from a set of repositories. Generally, they consist of two connected tiers: an aggregation system for populating an information space of metadata records by harvesting and transforming (e.g., cleaning, enriching) records from a set of OAI-PMH compatible data sources, typically repositories; and a web portal, providing end-users with advanced functionality over such information space (search, browsing, annotations, recommendations, collections, user profiling, etc). Typically, information spaces also offer access to third-party applications through standard APIs (e.g., OAI-PMH, SRW, OAI-ORE). Repository infrastructure systems address similar architectural and functional issues across several disciplines and application domains. On the one hand they all deal, with more or less contingent complexity, with the generic problem of harvesting metadata records of a given format, transform them into records of a target format and deliver web portals to operate over these records. On the other hand, they have to cope with arbitrary numbers of repositories, hence administering them, from automatic scheduling of harvesting and transformation actions, definition of relative transformation mappings, to the inherent scalability problems of coping with ever growing incoming records. Existing solutions tend to privilege customization of software, neglecting general-purpose approaches. Typically, for example, aggregation systems are designed to generate metadata records of a format X from records of format Y, and not be parametric with respect to such formats. Similarly, the participation of a repository to an infrastructure is driven by firm policies and administrators often do not have the freedom of specifying their own workflow, by combining as they prefer logical steps such as harvesting, storing, transforming, indexing and validating. In summary, repository infrastructure systems typically provide advanced and effective solutions tailored to the one scenario of interest, while can hardly be applicable to different scenarios, where similar but distinct requirements apply. As a consequence, an organization willing to set up a repository infrastructure system with peculiar requirements has to face the "expensive" problem of designing and developing a new software from scratch. In this paper, we present a general-purpose and cost-efficient solution for the construction of customized repository infrastructures, based on the D-NET Software Toolkit (www.d-net.research-infrastructures.eu), developed in the context of the DRIVER and DRIVER-II projects (http://www.driver-community.eu). D-NET offers a service-oriented framework, whose services can be combined by developers to easily construct customized aggregation systems and personalized web portals. D-NET services can be customized, extended and combined to match domain specific scenarios, while distribution, sharing and orchestration of services enables the construction of scalable and robust repository infrastructures. As we shall describe in the following, D-NET is currently the enabling software of a number of European projects and national initiatives
Repository sustainability: arXiv business model experience and implications
Get PDFIn January 2010 Cornell University Library moved to expand the funding base for arXiv by requesting support from user institutions. We hope that this voluntary support model will engage the institutions that benefit most from arXiv while maintaining arXiv's open access mission as a service free to readers and submitters alike. The development of a business model has made us look closely at arXiv's sustainability from both operational and technical standpoints. The engagement of supporting institutions creates new requirements to demonstrate value to these institutions as separate from arXiv's understood value to the community in general. In this presentation we will briefly describe options considered in development of the business model, the model chosen, uptake and feedback. We will then focus on the implications for arXiv's operation, for the long term development of our platform, and new reporting facilities
Research reporting using Eprints at The University of Northampton
Get PDFEach year The University of Northampton research administrators produce an "Annual Research Report" for each of the university's six Schools. Before 2007, and in the absence of any centralised research database, research details were simply collated and word-processed into one-off documents. NECTAR provided the opportunity to store bibliographic details in a systematic manner and the potential to re-use these data for research reporting
Towards Interoperable Preservation Repositories (TIPR)
Get PDFThe TIPR Project, Towards Interoperable Preservation Repositories, was begun in October 2008, its participants being the Florida Center for Library Automation, the Bobst Library at New York University, and Cornell University Library. Our goal has been to develop, test, and promote a standard format for exchanging information packages among dissimilar preservation repositories - an intermediary information package that all repositories can read and write, overcoming the mismatch between repository types
Author identifiers: 1) Services at arXiv and 2) ORCID and repositories
Get PDFI will present two separate but related topics where experience with the first provides much of my perspective with the second.
Public author identifiers and services based on them were introduced in March 2009 and early work and design was reported at OR09. The original services have been running for a year now and additional facilities have been added. I will report and uptake and usage patterns, and describe the more popular services.
ORCID is an exciting initiative involving both commercial and academic participants that aims to build a registry and assign identifiers to address the author ambiguity problem. I will report on the current status of this rapidly evolving project and suggest how the repository community may contribute to and benefit from it