Ana səhifə

National Library of Medicine Recommendations on nlm digital Repository Software


Yüklə 1.4 Mb.
səhifə15/15
tarix10.06.2016
ölçüsü1.4 Mb.
1   ...   7   8   9   10   11   12   13   14   15

Response request - Demonstrate a response request is received from Coordinate Access Activities


7.6.3.4

A

Demonstrated retrieval of objects via the UI without issue.

Demonstrated retrieval of objects via the UI without issue.

2




8.1 Metadata Requirements




M
















8.1.1

Metadata formats - Demonstrate that the system can accept metadata associated with objects in at least the following formats: All NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI.

8.1.1

M/T

T=3 M=3

T=3 Any metadata could be added as a datastream; M=3.

T=3 M=3

Fedora is completely agnostic about what kinds of metadata and number of metadata objects that can be assigned to any object

8.1.2

Metadata checks - Demonstrate the built-in checks on the incoming metadata. Records not containing the minimally defined set of fields should be flagged as problems, either to be returned to the submitter, or sent locally for metadata enhancement.

8.1.2

M

3

3




3

Fedora would need an additional tool to perform checks.

8.1.5

Metadata updates - Demonstrate the ability to allow for metadata updates.

8.1.5

M

3

2.5




3

Fedora client only has one template field for descriptive title; actual object metadata box can take anything just need disseminator to do something with it.

8.1.6a

Metadata search and display - Demonstrate the ability to search and display metadata (use of external tool possible).

8.1.6a

M

3

2.5




3




8.1.8

PREMIS - Demonstrate standards compliance for PREMIS (use of external tool possible).

8.1.8

M/T

T=3 M=3

T=2 Fez limited. Fez won't display Premis metadata if it was added in Fedora. M=2

T=3 M=3

Fez creates PREMIS metadata for each object, stored as Fedora datastream in the object.

8.1.9

METS - Demonstrate standards compliance for METS (use of external tool possible).

8.1.9

M/T

T=3 Fedora can ingest METS SIPs, and export objects in METS format. M=3

T=1 Fez limited. METS could be stored as a datastream. M=2

T=3 M=3

Fedora can store METS metadata as a datastream in an object, e.g. to drive a METS-based page-turner.

App A

Descriptive metadata - Demonstrate that the minimum descriptive metadata requirements described in Appendix A are accepted.

App A

M

3

2




3




9.1 Additional Technical Infrastructure Requirements




T
















9.1.1

OAI-PMH - Demonstrate that the system can respond to OAI-PMH requests as a data provider.

9.1.1

T

2

0




2

Fedora has a basic OAI-PMH capability, and an extended capability using the optional OAI-Provider tool (in the Fedora Service Framework).

9.1.2

Z39.50 - By design analysis, confirm that the system can respond to data requests using the Z39.50 standard.

9.1.2

T

0

0




0




9.1.3

SRU/SRW - By design analysis, confirm that the system can respond to data requests using the SRU and SRW data access standards.

9.1.3

T

0

0




0

VTLS provides SRU/SRW for Arrow project.

9.1.4

SOAP - Demonstrate that the system can respond to web service requests using SOAP.

9.1.4

T

3

0




3




9.1.5

UNICODE - Demonstrate that the system supports UNICODE.

9.1.5

T

3

2




3

UNICODE filename not displayed properly in Fez. UNICODE file content handled ok.

9.1.6

OpenURL - By design analysis, confirm that the system is compliant with OpenURL.

9.1.6

T

0

0




0




9.1.7

Z39.87 - By design analysis, confirm that the system supports the Z39.87 image metadata standard.

9.1.7

T

0

0




0


























































Notes:

1. Subgroups: A=Access, M=Metadata, P=Preservation, T=Technical Infrastructure






















2. Score indicates the extent to which the test element could be demonstrated: 0=None, 1=Low, 2=Moderate, 3=High













3. Preservation tests - These sections of the functional requirements are covered by Test Plan sections P1, P2, and P3, which were defined by the Preservation subgroup to facilitate testing.




4. Test elements having blue background are the subject of outstanding questions from the Access subgroup.










1   ...   7   8   9   10   11   12   13   14   15


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©kagiz.org 2016
rəhbərliyinə müraciət