• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Project: RIP overview

Page history last edited by Amanda Focke 10 years, 9 months ago Saved with comment

Project: Rice Institute Pamphlets / Rice University Studies

https://scholarship.rice.edu/handle/1911/8324

 

Basic overview:

PDF files of of the Rice Institute / Rice University publication which is no longer published. It was published in annual volumes with quarterly issues, each containing a Table of Contents and various articles.

 

Collection attributes:

  • Custom structure and metadata needed for presentation of series publications

 

Project handled in two parts:

Part 1: Rice Institute Pamphlets, Vols. 1-33 (1915-1946), a very early digital project project at Fondren (2004), put into previous digital asset management system associated with SIRSI, called "Hyperion". This hierarchical collection was then flattened and put into current IR (dspace) with a simple default interface.Tech Services and WRC did the original metadata directly in the Hyperion system.

 

Part 2: Rice University Studies, Vols. 34-66 (1947-1980) done in 2010-2011, with WRC created metadata in a spreadsheet for batch ingest into dpsace, Fall 2011.

 

Metadata edit work

 

Current status:
All materials are in dspace, and a new more user-friendly interface has been applied, which uncovered some metadata quirks which needed to be standardized. Completed Nov., 2011.

 

Notes for Rice Institute Pamphlet (RIP) Interface

To generate hierarchical interface for RIP, there are some restrictions on metadata we need to follow.

 

Before we go through the details of those metadata, I’d like to have an overview of the process for generating the interface.

 

The first step would be creating an XML with all hierarchical relationship of the collection. The script in this step needs to be run whenever you have relationship changed on Volume/Issue level.

 

And then an XSLT script will parse the XML and generate the appropriate interface we desired. 

 

There is no need of restarting the server on these changes.

 

 

Restricted Metadata –

dc.citation.VolumeNumber – The issue items with same VolumeNumber will be pulled together in the same Volume row.  Accept Value: Numbers (can’t be null), e.g. “46”

Special Handling so far – “Index”, “48-49”.

 

Any value other than a number right now needs special handling to have it properly displayed.

 

 dc.citation.IssueNumber – An item with VolumeNumber, IssueNumber but not PageNumber is considered as an issue item and will be placed on the row of the same Volume. A link is provided to search for the items under the issue.

Accept Value: Numbers, e.g. “2”

Special Handling so far – “Special Issue”, “Supplement”.

 

Any value other than a number right now needs special handling to have it properly displayed.

 

dc.citation.PageNumber – The items with PageNumber are ignored in the script.

 

dc.relation.ispartofseries – Part of the field needs to be normalized as following so that the item can be searched.

 

e.g. “Volume 5, Number 4”

 

This exact format needs to be followed including space J

The string is assembled with “Volume” + dc.citation.VolumeNumber + “, Number “ + dc.citation.IssueNumber

 

Again, there are special handlings for Issue “Special Issue” and “Supplement”.

 

Any values in VolumeNumber and IssueNumber that make the sentence look different than what we shown above may need special handling.

Comments (0)

You don't have permission to comment on this page.