DefiningImageAccess/Project/MIDESS
From ImageWeb
| DefiningImageAccess/Project/MIDESS | |
|---|---|
| homepage:=http://www.leeds.ac.uk/library/midess/}} | |
| [[has sub-project::{{{Subproject}}}]]}} | |
| [[sub-project of::{{{Supproject}}}]]}} | |
| [[start date:={{{Start date}}}]]}} | |
| [[end date:={{{End date}}}]]}} | |
| Status:=Initial Stage}} | |
| JISCProject:=True}} | |
| Image Materials:=2D, 3D, and videos}} | |
| Focus:=Metadata Creation, Harvesting}} | |
| Publishes::DefiningImageAccess/Resource/MIDESS}} | |
| [[References::{{{References}}}]]}} | |
| [[Uses::{{{Uses}}}]]}} | |
| [[Creates::{{{Creates}}}]]}} | |
| [[Partner::{{{Partner}}}]]}} | |
| [[Contact::{{{Contact}}}]]}} | |
MIDESS Project
Management of Images in a Distributed Environment with Shared Services
Description
A JISC funded project exploring the management of digitised content in institutional and cross-institutional contexts through the development of a digital repository infrastructures. The project will run for 2 years from 1st June 2005.
Stakeholder: University of Birmingham | University of Leeds | London School of Economics | University College London
Data Objects: digital images that have been created or being created at the moment, including images from slides and manuscripts]]; multimedia content such as audio, video
MIDESS is concentrating specifically on software oriented towards the management of multimedia materials and digitized images. They claim "Issues such as metadata creation and management, effective searching and retrieval, re-use of content in an e-learning context and digital preservation are also poorly understood and not widely implemented."
dia:tag:=Issues with creating digital materials:
- reluctant to learning new softwares and technologies.
- There is a very low awareness of copyright legislation amongst respondents.
- They are not happy with the overload when searching for materials by the external search engines, such as Google.
- Metadata of these materials is rarely provided.
- The materials are rarely shared due to the reasons of short of time, security, copyright, data protection, etc.
- The technical staffs regarded the boundary for reusing the materials is the fact that much of the material was primarily intended for use within the university rather than for wider distribution.
- This project makes minimal reference to the Web as a platform, but the following appears in the Recommendations section of the User Requirements Analysis, under Technical Requirements: "The repository should be capable of referencing externally held content on other servers" (section 7).
- The project makes specific reference to the METS metadata standard, as well as others.
Contact: Tracey Stanley, Project Director (t.s.stanley) or Stephen Charles, Project Manager (S.J.Charles), both (@leeds.ac.uk).
Observations
We've spoken to someone who is involved with the MIDESS project. Apparently they have tried transferring digital objects between repositories using METS wrappers, and so far failed to achieve usable interoperability. We hear that either the standards enough are not, of themselves, sufficiently well specified to promote interoperability, or the implementations are not faithful to the specifications. It is not clearb from our discussions whether the incompatibilities are primiarily syntactic (generating badly-formed packages, or failing to parse well-formed packages) or semantic (using diferent metadata elements, requiring elements not provided, or rejecting well-formed but semantically unrecognized elements) in nature.
I suspect that this is a problem with depending on a "wrapper" specification, with insufficient attention to agreement on elements to be used within that framework.
It is possible that the extensibility model is not sufficiently well definied or supported, leading to problems of adaptation between different levels of support. (This could be as simple as defining a minimum core requirement and adopting a principle of ignoring any unrecognized elements beyond that.)
