DRAFT Scoping Report
V1 – July 2006
service against legal action relating to the content of the e-print. There should be not time limit;
during its period of operation, Prospero may put back any e-print that is successfully defended by
11. Authentication and authorisation issues
Question: What authentication and authorisation are required?
Recommendation: Athens and/or Shibboleth should be used to establish institutional membership,
or “eligibility”, for user registration. A validated email address will be required for registration, to
ensure communication with the user is possible. Registered users will have a Prospero user
identity, which could (subject to policy) be transparent to the user, or could enable Athens/Shibboleth
identifiers and email addresses associated with that identity to be changed.
12. Software selection
Question: What software should be used for the repository?
Recommendation: A) E-prints implementation to continue on to main phase, with scoped options
implemented in the system and interface. A technology watch will determine if a move to a new
system is required during the life of the project.
13. OAIS Reference Model and digital preservation
Question: To what extent will the interim repository conform to the OAIS reference model and how
will this assist digital preservation of deposited objects?
B) Implement the repository software ‘out of the box’, in order to get a
quick start. Make any improvements through upgrades, planning and policies, and
monitoring environment that resources allow. Focus on the ‘self’ in self-archiving; make
the depositor responsible for the integrity of what is deposited. SIP, AIP, and DIP may end
up being exactly the same.
It is expected that migration decisions will not need to be
taken by the interim repository because file formats will be limited to those expected not to
become obsolete within the 5 year planning horizon. Limit human intervention to a
minimum level, but investigate tools such as JHOVE for checksums and format checks on
ingest, in case file integrity is in question at time of transfer.
14. Subject classification
Question: What – if any— subject classification scheme should be implemented in the national
Recommendation: B) We recommend using JACS because it was invented by HESA to
correspond to UKHE, it condenses to a reasonable size at the top level for depositors and readers to
understand, and because it was implemented successfully by JORUM.
Question: Which metadata standards should the repository facility adopt?
Recommendation: A) For descriptive data to allow discovery by users, the depositor will enter
Dublin Core fields within the deposit interface to the software. These fields should be mandatory.
Recommendation: C) The repository staff will investigate the use of preservation metadata such
as METS, MODS, PREMIS, MPEG21-DIDL, and its implementation within or outwith the repository
software for purposes of audit trail as well as for the transfer service during the life of the project, and
will adopt new practices as recommended by further investigation/scoping.
16. Document type and file format policy
“For repositories, it is conceivable, although perhaps unlikely, that the SIP, AIP and DIP are all the same, that a submitted
package is ingested, stored and delivered in an unchanged state. There is nothing in OAIS to say that this should not happen,
so long as the necessary information is captured at submission. (Allinson, p. 12.)