Archive Workshop on Ingest, Identification, and Certification Standards (AWIICS)
(A part of the ISO Archiving Workshop Series)
1. Identification of Proposed or Existing Effort
1.1 Title
[No title was developed for the effort]
1.2 Contributor(s)
Library Community
Electronic records community
Scientific Archives
Traditional Archives
1.3 Description of Effort
· Develop scenarios of archive usage of identifiers.
· What is purpose of identifier?
· Are identifiers even needed?
· Provide Requirements
· Provide Interoperability Standards for Archives
1.4 Justification
Experts from various communities have been unable to arrive at a consensus on the following questions:
+What is an identifier? How does it relate to name and metadata and instance of content or location?
+What is an archive?
+What kind of standards body effort would lend itself to an identification model for access and portability?
+What is a repository? How do archive and repository differ in the electronic environment?
+What are the new responsibilities of an archivist in an electronic archive?
+How is the responsibility of archive preservation or duty of care changed for an electronic collection and/or object?
+How does the submission of electronic objects to an archive change the requirements for identification?
1.5 Definitions of Concepts and Special Terms
Definitions needed for :
· Archive
· Identifier
· Units to be identified
· Collections
Some definitions were given as follow:
Naming authority: organization which assigns
invariant parts of identifiers
Registration authority: synonym highest level Naming authority, Also establishes procedures, standards and policies
----------------------------------
2. Scope of Proposed Effort
2.1 Recommended Scope
Digital Archives and Libraries, Access and Identification
2.2 Existing Practices
- NARA Practices e.g
- Census data
- Science archives practices, e.g.,
- MEDLARS
- Human Genome project
- OCLC Practices
2.3 Expected Stability of Proposed Product with Respect to Current and Potential Technological Advances
Perpetuity, insensitive to technology changes
Implementations changed by technology changes.
----------------------------------
3.0 Standardization Effort
3.1 Recommended Program of Work
Develop Group
Prepare Proposal
Develop Scenarios -------------------9th month after AWIICS
Workshop to evaluate Scenarios------11th month
Develop requirements ---------------15th month
Community Review / e-mail
Develop appropriate procedures, practices, data structures, and services to enable interoperability.
3.2 Resources - Individuals and Organizations Competent in Subject Matter
See communities above.
3.3 Recommended Standards Development Organization (Existing or New)
CCSDS Panel 2
NISO
AIIM Int’l
IFLA
ARMA
SAA
ICA
W3C
IETF
Consortium of Digital Archives (new)
3.4 Anticipated Frequency and Duration of Meetings
- US meetings 6 times per year
- International meetings 2 times per year
3.5 Target Date for Initial Public Review
TBD
3.6 Estimated Useful Life of Standard Perpetual
----------------------------------
4. Implementation Impacts
4.1 Impact on Existing User Practices and Investments
The goal of standards activities is to be compatible with legacy systems.
4.2 Impact on Supplier Products and Support
The goal of standards activities is to be compatible with existing and future products
4.3 Techniques and Costs for Conformity Assessment
Anticipate a test suite that produces repeatable results.
4.4 Legal Considerations
TBD
----------------------------------
5. Closely Related Standards Activities
5.1 Existing Standards
Dublin Core
URI efforts
DOI
X.500
GILS
CNRI Handles
TC211 (Geomatics)
Z39.50
5.2 U.S. Standards Development (SDO) Organizations Projects
URI efforts
DOI
X.500
GILS
CNRI Handles
)
5.3 Other Related International Standards Development Projects
ISO /IEC JTC 1 9594-1
CCSDS Panel 2
5.4 Recommendations for Close Liaison
All of above able to contribute