Project – Overlay journal infrastructure for Meteorological Sciences (OJIMS)

Project Name:

Overlay journal infrastructure for Meteorological Sciences

Short Project Name:OJIMS

Programme Name:Repositories and Preservation

Strand: SUE

JISC Project URI:http://www.jisc.ac.uk/whatwedo/programmes/reppres/sue/ojims.aspx

Project URIhttp://proj.badc.rl.ac.uk/ojims

Start Date: 1 March 2007

End Date:28 February 2008

Governance: JISC IEEE

Contact Name and Role: Sam Pepler (Project Manager)

Brief project description:

The main aim is to develop the mechanisms which could support both a new Journal of Meteorological Data and an Open-Access Repository for documents related to the meteorological sciences.

Name of Trawler: Mahendra Mahey

Outputs: (just link to individual output postings) as a bulleted list:

  • An operational metrological document repository
  • Overlay journal software
  • A business concept description for the ‘Journal of Meteorological Data’ and the ‘RMetS kite-marking journal’
  • Recommendations for setting up subject based repositories and overlay journal infrastructure

Output – OJIMS – CEDA Repository

Output Name: Output – OJIMS  – CEDA Repository

Title: CEDA Repository
Date Released: Unknown

URI for Output: http://cedadocs.badc.rl.ac.uk/

Summary of contents: ‘Information in this repository is grey literature primarily concerning Earth observation and atmospheric sciences.’ The Centre for Environmental Data Archival (CEDA) is based at the STFC Rutherford Appleton Laboratory and hosts a range of activities associated with environmental data archives.

Output – UHRA – University of Hertfordshire Research Archive

Title: The University of Hertfordshire Research Archive

Date Released: Approx September 2007

URI for Output: https://uhra.herts.ac.uk/dspace/

Summary of contents:

The main output from this project is the establishment of the University of Hertfordshire Research Archive. It is described as “.. a showcase of the research produced by the University of Hertfordshire staff (copyright permitting) which is freely available over the web” and ” .. provides a simple interface to enable researchers to self-archive the full text of their published work with just a few quick and easy steps.”

Additional information:

Comments:

The archive/repository appears to be fully functional and contains 2556 items as at 30th January 2007.

Project – CIRCLE

Short Project Name: Common Institutional Repositories for Collaborative Learning Environments (CIRCLE)

Programme Name: Repositories and Preservation programme

Strand: Information Environment

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/reppres/sue/circle

Project URI: https://mw.brookes.ac.uk/display/circle/Home

Start Date: 1st Feb 2007

End Date: 31st July 2008

Governance: RPAG

Contact Name and Role: Stuart Brown, Project Manager

Brief project description:

Exploring the organisational, cultural, procedural and technical challenges in creating a singular repository to fulfil the roles usually provided by discrete Learning Object Management, Open Archive and scholarly repository systems. Delivering these systems into live operation. Collaborating with Intrallect to accelerate development. Advancing understanding and acceptance by the dissemination of the results of our work through the JISC programmes structures.

Outputs:

  • Establish Learning Object Management system.
  • Establish repository to hold and make available Brookes research outputs as an Open Archive.
  • Situate these developments within processes encouraging collaboration, self-direction and sharing.
  • Explore the wider relationship between these repository applications and other content management and collaborative technologies.
  • Share the experience and promote an advance in thinking on the relationships between repository types and their integration with complex and diverse user communities.

Comments:

No significant outputs found as at 22nd January 2009 other than project website and conference presentations.

Output – FAR – Adding Shibboleth to DSpace With CASAK

Output Name: Output – FAR – Adding Shibboleth to DSpace With CASAK

Title: Adding Shibboleth to DSpace With CASAK
Number of pages or page numbers: webpage

Date Released: unknown

URI for Output: https://dspace.far-project.lse.ac.uk/casak-shib.html (report) for

patch – https://saffron.caret.cam.ac.uk/svn/projects/far/trunk/

Summary of contents:

CASAK is a patch for DSpace which allows container auth to be integrated into DSpace. It provides a number of mapping and filtering facilities to transform data provided by the container into a form suitable for DSpace. These facilities are generally inferior to those available within the SP, but for simple cases the configuration is perhaps simpler.

Configuring CASAK to use Shibboleth is therefore simpler than many use-cases of CASAK.

The approach used here contrasts with that used in MAMS in that CASAK is not Shibboleth specific, and has been designed to make a range of container auth solutions possible with CASAK. The purpose of this was to increase the long-term sustainability of the patch by extending its application to as broad a user-base as possible.

Output – FAR – LDAP server containing sample users with these attributes

Output Name: Output – FAR – LDAP server containing sample users with these attributes

Title: LDAP server containing sample users with these attributes
Number of pages or page numbers: webpage

Date Released: 29 June 2008

URI for Output: https://gabriel.lse.ac.uk/twiki/bin/view/Projects/FAR/FARProjectDemonstratorArchitecture

Summary of contents:

Technical description of the FAR Demonstrator Architecture.

Output – FAR – FAR attribute requirements report

Output Name: Output – FAR – FAR attribute requirements report

Title: FAR attribute requirements report
Number of pages or page numbers: webpage

Date Released: 19 August 2008

URI for Output:  https://gabriel.lse.ac.uk/twiki/bin/view/Projects/FAR/AttributeUseReport

Summary of contents:

  • Requirements for specific attributes to be used for Federated Access Management (FAM)-mediated access to repositories are not necessary because repository products use groups for access control already
  • It is recommended that group membership information is structured in attribute stores on a per-user basis (with a user object containing a list of groups of which the user is a member) as opposed to solely as a per-group basis (with a group object containing a list of members)
  • The use of groups for authorisation means that it should be possible for FAM to continue to be applicable with the introduction of new features to repository software