| Library home | Catalogue | Resources | Services | Help | Libraries | About us |
| Staff directory | A-Z index | Site map |
| Library home | Catalogue | Resources | Services | Help | Libraries | About us |
| Staff directory | A-Z index | Site map |
University projectsContent Management System (CMS) projectMonash University commenced implementation of a web content management system in 2003. Enterprise Content Management products from Interwoven, Inc., were selected for this project. For more information about this project see ITS Web Content Management System, CMS TeamSite and CMS Metatagger CMS Metadata Working PartyIn the early stages of the project the CMS Metadata Working Party was formed consisting of university wide membership. The group was charged with developing a CMS metadata strategy and then a metadata standard and a community-specific controlled vocabulary for resource types for the early implementation of metadata in the CMS. CMS metadata strategyAn effective metadata strategy was outlined by the group. It was agreed that:
CMS metadata standardThrough 2003 a metadata standard based on DC / AGLS was developed. CMS metadata elements and guidelines document was endorsed by the Web Steering Committee in 2004. This is a work in progress and will be updated as international / national / local standards are revised and as the Metatagger product is implemented. MetaTaggerMetaTagger is part of a suite of web content management products provided by Interwoven, Inc. MetaTagger's intelligent set of tools automatically categorises and tags content and extracts information through the use of controlled vocabularies and business rules. For more information including product benefits, functionality and other relevant details see the university CMS MetaTagger page, and, a product description at the Interwoven website. CMS metadata implementationWe have so far only implemented a minimal subset of metadata. This is applied manually and is part of the workflow for web authoring. The approach we want to trial is to make metadata available automatically for editing by the author. Our initial focus has been to implement TeamSite web content management and our implementation of the related product MetaTagger is progressing very slowly, hence a minimalist approach to metadata so far. PresentationMetadata at Monash was presented by the Metadata E-Cataloguing Coordinator and the Library Web Manager as part of the ITS Web Workshop series In September 2004. ARROW projectARROW (Australian Research Repositories online to the World) project is funded by the Australian Department of Education, Science and Training. The ARROW consortium consists of Monash University as the lead institution working with the National Library of Australia, Swinburne University of Technology and the University of New South Wales. The ARROW project will identify and test software or solutions to support best-practice institutional repositories including e-prints, digital theses and electronic publishing. A wide range of digital content types will be managed in these repositories. See:
ARROW metadata strategyThe ARROW strategy does not require the use of a single metadata schema to describe all digital objects stored in the repository. Multiple formats to suit individual content models can be supported. OCLC and ARROW are working together to test a mapping tool developed by OCLC called the Interoperability Core which is based on mappings and crosswalks between different metadata formats.Metadata can be stored and searched in the native format generated by the community of practice. Using this strategy ARROW can be populated with metadata from a variety of formats and through various mappings converted to an interoperable core which can then be converted to DC for harvesting via OAI-PMH (Open Archive Initiative Protocol for Metadata Harvesting) by resource discovery services.
The OCLC Metadata Interoperability Core, from Godby, Carol Jean, Devon Smith, and Eric Childress. 2003. "Two Paths to Interoperable Metadata." Available online at http://www.oclc.org/research/publications/archive/2003/godby-dc2003.pdf; and, also referenced in Geoff Payne's Educause Australasia 2005 Presentation, Auckland, 7 April 2005. ARROW Persistent IdentifiersARROW has selected the Handle System persistent identifier scheme. For more details about handles see the Handle System site. ARROW Data ModellingThere are no agreed standard data models for objects in institutional repositories. Specifications for data models will be based on use cases for any given class of objects. Simple objects such as an image may require just descriptive metadata while more complex objects such as a book, a thesis may require descriptive as well as administrative and access control metadata or additional technical metadata may be required for an object stored for preservation purposes. Monash ARROW ImplementationThe Monash ARROW implementation team was set up in July 2004 and held its first meeting in August 2004. Monash content projects were identified and timelines established for project deliverables. In November 2004 training in Vital / Fedora software (software chosen to manage digital objects in the ARROW institutionalrepository) was undertaken by appropriate Monash staff with staff from partner institutions and facilitated by VTLS trainers. Monash ARROW Content Projects (tasks ongoing)
More projectsSee the Projects page at the DCMI website for information about other Australian and overseas metadata projects. Need help? Library frequently asked questions and online
enquiries: current students/staff | public users, online chat,
or phone +61 3 9905 5054 |
