Business Requirement: Collection Building
Business Business Business
Process Function SubFunction
Collection
Ingest
Batch
Import Customization
Gap analysis rating by DRS Imp. Team* (see key below)
Comments
Short
Long Notes*
term*
term*
Gaps:
Could not process non-roman
scripts
Could not validate content
based upon schema
D
E
D
HD
Current Functionality:
Multiple Target Modes
Marc Ingest
Ingest based upon data token
Ingest Output from executable
program
Interface
Gaps:
Requirements for a web based
user Interface to the existing
scripts for batch ingest:
Interface must support:
(1) non roman scripts
(2) unicode
(3) Qualified DC
-1-
Have Webapp for drag & drop
ingest of directories
Technical
Metadata
Capture
Submission
Packaging
Logging and
Audit
(4) Must validate content based
upon xml schema
(5) Must be supported at the
collection level
Batch import captures some
technical metadata
automatically
Gap:
Batch Interface needs option to
create METS or FOXML
Package
Gap:
Batch Import must have logging
and audit report capability
Collection level batch import
-2-
D
HD
D
HD
HD
E
HD
E
Via JHOVE
Business Business Business
Process Function SubFunction
Interface
Ingest1
Batch
Edit, i.e.,
global
change
Object
Selection
Workspace
1
Comments
Short
term
Long Notes
Term
Requirement:
Must be accessed via the
Administrative Interface
All batch edit function must be
unicode compliant
Requirement:
The tool will require a way of
selecting objects from the
repository. This will be a search
result set where particular
objects can be individually
selected out of the results list, or
the whole result set can be used
Requirement:
Selected objects will be edited in
a buffer area
D
E
Does not exist now so individual
sub-functions are not ranked.
Batch edit was unavailable and not analyzed during the research investigation; analysis shows likely usage by collection.
-3-
Metadata
Modification
Preview
Requirement:
Edit functions must include find
and replace metadata in
specified metadata datastreams;
must also operate at global level
on these operations:
• Delete datastream(s).
• Add datastream(s).
• Set access restrictions for
object and or datastreams.
• Change the object’s content
model.
• Change the object’s
collection relationships.
Requirement:
The tool will include a review
stage to preview
the changed objects in buffer
area. User is prompted to accept
or reject changed objects.
-4-
Busines
s
Process
Ingest
Business Business SubFunction Function
Work
flow/
self
submiss
ion
Templates
Interface
Customization
Comments
Short
term
Long
Term
Notes
Gaps:
Templates can not be easily
changed
Stylesheets were not accessible
D
E
“Valet”
D
HD
D
HD
Existing Functionality
Templates for e-theses and
dissertations
Configurable templates and
workflows
Configurable workflow and
staged review
Metadata transformation for any
XML schema
Auto assignment of Handles
Full text extraction of PDF files
for indexing
Help Windows
Gap:
A Web Based User Interface for
configuring, customizing, and
generating self-submission/
deposit templates.
Gaps:
Customization of workflow by:
Display order of data entry fields
Associating controlled vocabs
-5-
with certain fields
Preferred data entry field type,
e.g. drop down list, free text and
Mandatory fields
Business Business Business
Process Function SubFunction
Modalities
Ingest
File
Import
Submission
Packaging
Logging and
Audit
Comment
Short
term
Long
term
Note
Existing Functionality
Add files from local file system
Drag and drop from local file
system
Add files from track folder
Existing Functionality:
File import modality has option
to specify METS or FOXML
import object
n/a
n/a
Function exists, rating n/a
Existing Functionality:
Fedora File import has audit and
logging capability
-6-
Busine Business
ss
Function
Process
Access Search/
Index
Public
Interfa
ce
Business SubFunction
Comment
Short
term
Long
term
Interface
Gaps:
Could not create collection
(Search and Index defined at the
repository level. Cross collection
search not possible.)
E
E
D
HD
Interface,
continued
.
Easy index definitions (Adding
elements to index was
complicated and required
knowledge of xml.)
Interface,
continued
Advanced navigation ability of
search results was limited.
D
HD
Interface,
continued
Correct handling of Romanized
text w/ diacritics and special
characters. (Special characters
not retrieved properly.)
Support for vernacular (UTS-8)
including right-to-left. (The
search and index function also
lacked the ability to handle non
roman languages like Arabic)
E
E
HD
E
Interface,
continued
-7-
Notes
Others way to solve this
available.
Interface,contin
ued
Support for Romanized test w/
diacritics
E
E
Gaps:
E
Creation of structured metadata
defining relationships. (It is
required that structured metadata
be attached to the relationship
between entities in addition to
being attached to the entities
themselves.)
Object Relationships
Objects can be related to one
another and other types of
datastreams
Relationship Query
Requirements
Queries based upon relationships
must be supported
VITAL Manager Gaps:
D
Vital Manager/Administrative
interface must allow the
repository manager to search on:
Any attribute of an objects and at
the field level
and across collections; Preserve
search history
E
Relationships
-8-
D
Business Business Business
Process Function SubFunction
Access
Harvest Data Provider
Service
Provider
Comment
Short
term
Long
term
Notes
VTLS/VITAL is OAI-PMH
enabled as a data provider
None of the collections analyzed
include service provision.
Services are likely to be required
in the future. Metaindex is
currently used for this function.
HD
E
Works in the field. What
beyond Dublin Core?
D
E
Business Business
Process Function
Business
SubFunction
Comment
Short
term
Long
term
Access
Customized
Rendering
Gaps:
Customized presentations were
restricted in VTLS/VITAL. The
ability to create use case specific
interfaces into Fedora through
customized disseminators is
technically possible.
VTLS will allow customers to
build their own disseminators in
VITAL 2.1.
HD
E
Presentation
-9-
Notes
Business Business
Process Functions
UTF-8
Batch
Import
Client
ingest,
Comment
Gaps:
UTF-8 must be loaded and
maintained with complete
integrity
Short
term
E
Long
term
E
E
HD
E
E
E
E
File
Import,
Search/
Index
Harvest
Ingest of URF-8
Access / display of UTF-8
Romanized text w/ diacritics
- 10 -
Notes
KEY
Term
Explanation
Notes
D
Desirable
Desirable items not available will add to investment of
staff time in short term
HD
Highly Desirable
E
Essential
Short term
Initial implementation
Showstopper
- 11 -