Category: Dspace

  • DSpace REST API built in JERSEY

    I thought I’d take a quick moment to highlight some work that was done by one of the programmers here at The OSU, Peter Dietz.  Peter is a bit of a DSpace wiz and a contributor to the project, and one of the things that he’s been interested in working on has been the development…

  • Using MarcEdit to reuse (and maybe import) items in Dspace

    I’ve been thinking a little bit about some of the things that I use MarcEdit for and have been pushing some of this work off my desk to some of the staff in our technical services department.  We actually use MarcEdit quite a bit when it comes to sharing metadata from our Dspace instance with…

  • Translating ETDs from Dspace OAI to MARC

    Ok — here’s the info.  File: MidWinter 2007 ALCTS PresentationSo what’s included?  Zip file contains our custom XSLT that’s used in MarcEdit, the Macro that I use to clean data, and the ppt slides.  The XSLT file is a custom version of the default OAIDC translation found in MarcEdit.  Its customized to deal with the…

  • Dspace Community-list; adding most popular collections entries hack

    As I’ve started to get more involved in the Dspace work here at OSU, one thing that has struck me is the interface really could use a once over.  No place could this be more obvious than the community-list page.  While I doubt that this page was every meant to be the default access mechanism…

  • Dspace hack #2 — Did you mean?

    Its funny how things work out.  As some folks know, we are currently in the process at OSU of re-writing our hybrid metasearch tool from PHP to ruby, and now that much of the heavy lifting has been accomplished (a simple caching engine, wsdl api, oai harvesting, ferret integration, etc.), its been time to start…

  • Shifting through the chaos (myDspace pooled tasks)

    At OSU, we have very few Dspace collections configured to allow direct submission to the repository.  Nearly anyone on campus can submit an item into Dspace, but that item is then vetted through Technical Services where metadata is looked at and corrected before being added to Dspace.  To do this, we have ~4 individuals (though…