Ana səhifə

National Library of Medicine Recommendations on nlm digital Repository Software


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

Manage relationships - Demonstrate access rights and conditions can be inherited from a parent object to any child object.

7.6.1.13

A

XACML policies can utilize the RELS-EXT values to allow or deny access.

Security settings allow for parent-child propagation of security values.

2




7.6.1.14

Manage relationships - Demonstrate access rights and conditions can be assigned to an object on an individual or group basis at same time.

7.6.1.14

A

XACML policies can be assigned to a content model or by PID.

Child objects can inherit parent access controls or have their own independent controls. As with 7.6.1.8, this has not been successfully tested.

1




7.6.1.16

Automated retrieval - Demonstrate objects in the repository are accessible for data mining or automated retrieval.

7.6.1.16

A

Automated retrieval is not facilitated, but comprehensive indexing of metadata and fulltext is available with indexing plug-in.

Automated retrieval is not facilitated, but comprehensive indexing of metadata and fulltext is available with indexing plug-in.

1




7.6.1.17

Metadata access - Demonstrate access to deleted and retracted metadata is retained.

7.6.1.17

A

Fedora supports write-once, where any changes to datastreams are versioned.

Versioning of underlying datastreams is delegated to Fedora. Metadata, attached files and hyperlinks can be versioned through Fez.

1




7.6.1.18

Metadata harvesting - Demonstrate metadata harvesting following the OAI-PMH guidelines.

7.6.1.18

A

Fedora includes an OAI provider to expose content for harvesting. Recently rewritten for Fedora 3.0.

Fez can utilize the Fedora OAI provider.

1




7.6.1.10

Access rights - Demonstrate access rights and conditions of use are applied to each digital object and its related metadata and are machine readable and actionable.

7.6.1.10,

7.6.1.11


A

XACML policies are machine-readable by design.

Rights can be applied per datastream, object and higher-level aggregations.

2




7.6.1.12

Access conditions - Demonstrate access conditions are specific to a digital object.

7.6.1.12

A

Policies can be applied at the datastream level and all higher aggregations of content.

Rights can be applied per datastream, object and higher-level aggregations.

2




7.6.1.15

Free/Restricted access - Demonstrate free (items available via internal/external delivery mechanisms) and restricted access (access permission must be satisfy various criteria) status for objects, files, metadata, etc.

7.6.1.15

A

XACML policies can be written to allow or deny access at every level of object aggregation, using IP range, inactive/deleted status of datastreams, etc. Policies should be able to accommodate embargo logic ("moving wall").

Access controls are granular (in theory, unable to test successfully). No "embargo" logic is present.

2




7.6.1 Access - Coordinate Access Activities - Search and Retrieval




A
















7.6.1.19

508 compliance - Demonstrate the search interface is web-accessible and Section 508 compliant.

7.6.1.19

A

Fedora's thick client does not appear to be Section 508 compliant. However, NLM staff could use alternative methods for ingesting and managing content such as running UNIX commands or via a Web UI. Section 508 compliance is a design goal in any upcoming UI development.

Fez is an Australian product, so it is not bound by the Section 508 requirements. Since the product is open-source, NLM could easily tweak the HTML templates, etc. to create accessible UIs, etc. were feasible.

1.5




7.6.1.20

Search features - Demonstrate search includes: metadata, full-text, standard boolean, proximity, "more like" this"

7.6.1.20,

7.6.1.21,

7.6.1.22,

7.6.1.23,



7.6.1.24

A

Metadata searching with some operators, less GUI than Fez. GSearch supports full text indexing and searching, proximity.

No explicit "or" searching in our environment, but UQ has it. Lots of metadata searching, with wildcards. No proximity or "more like".

1




7.6.1.25

Search results display - Demonstrate search results display includes date sort; relevancy ranking; alpha by author or source.

7.6.1.25

A

no custom ordering of results. Default order is by PID.

No Author or source, but date, relevance, title, description.

2




7.6.1.26

Relevancy ranking - Demonstrate whether relevancy ranking can be manipulated via system as well as user defined settings.

7.6.1.26

A

n/a

Not accessible through admin interface.

0




7.6.1.29

Federated search - Demonstrate federated searching of different repository sites.

7.6.1.29

A




Can search across all or select communities/collections via advanced search.

2




7.6.1.30

Advanced search - Demonstrate advanced search includes search history; saved searches; saved citation lists/bibliographies; alerts; various functions and formats; dynamic selection of delivery media without recreating search query.

7.6.1.30

A

none of these functions are present

Can save searches as RSS feeds,

1




7.6.1.31

Display formats - Demonstrate a variety of standard display formats are provided and whether they are customizable by user

7.6.1.31

A

Fedora lets you select the fields to display.

Can be saved as XML, RSS, citation-only. Not customizable by user.

1




7.6.1.32

Alternate search interfaces - Demonstrate availability of alternate search interfaces for mechanisms such as handhelds and PDAs.

7.6.1.32

A










0




7.6.1.33

Object access - Demonstrate access to the appropriate copy of the identified item (text, image, video, etc.)

7.6.1.33

A

Datastreams have no preference.

Unclear how to identify the appropriate datastream, although one is highlighted. Can identify differences in datastream descriptions.

0




7.6.1.34

Library holdings - Demonstrate integration of search results with library holdings.

7.6.1.34

A










0




7.6.1.35

Response time - Demonstrate acceptable response time.

7.6.1.35

A

Response time is acceptable, within our test environment and limited collection.

Response time is acceptable, within our test environment and limited collection.

1




7.6.1.36

External search engines - Demonstrate searching by outside search engines such as usa.gov, Google, and Yahoo.

7.6.1.36

A

so far, evidence suggests only library web pages with a "browse view" external to Fedora are spidered.

uq.edu's espace browse pages appear to be indexed by Google

1




7.6.1.37

External system access - Demonstrate external access to other repositories or systems performing web harvesting functions.

7.6.1.37

A

Fedora has a built-in OAI-PMH Provider Interface, and all objects have a compliant DC record. Only the DC metadata may be disseminated, however.

Fez could delegate the OAI-PMH service to Fedora.

1




7.6.1.38

Language support - Demonstrate how multiple languages and non-Roman scripts are supported in search, retrieval and display.

7.6.1.38

A

Chinese characters do not display in test record (fedorans:137).

Chinese characters displayed in search results (fedorans:137), but not searchable.

1




7.6.1.39

Versioning - Demonstrate access to all versions of digital objects in the repository is provided.

7.6.1.39

A

Fedora objects can be versioned at every level, including disseminators.

All versions are accessible, but no versioning functionality for uploaded content. This is in the works for a future release.

2




7.6.1.40

Search settings - Demonstrate system settings and user-defined settings in the search functions are provided.

7.6.1.40

A

Only default system-provided search settings are offered.

Only default system-provided search settings are offered.

1




7.6.2 Access - Generate DIP




A
















7.6.2.1

Integrate holdings - Demonstrate integration of search results with library holdings.

7.6.2.1

A

No functionality built-in to Fedora for this.

No functionality built-in to Fez for this.

0




7.6.2.2

Retrieval and notification - Demonstrate the generation function accepts a dissemination request, retrieves AIP from archival storage and moves a copy of the data to a staging area for further processing, and creates and sends a report request to data management to obtain appropriate metadata.


7.6.2.2,

7.6.2.3,


7.6.2.4

A

AIP/DIP is conceptual, but the search API can result in a list of any and all datastreams, including all metadata associated with the object.

AIP/DIP is conceptual. Search interface can provide links to multiple derivatives of an object, the archival master and associated metadata.

2




7.6.2.7

Audit trail - Demonstrate an audit trail of all actions is created and stored.

7.6.2.7

A

Tomcat logs can provide dissemination requests (according to Indiana Univ. DLP).

Fez can track downloads per file, but this is not working in testing.

1




7.6.2.5

Response and delivery - Demonstrate that the prepared DIP response is placed in the staging area and a message is generated and sent to Coordinate Access Activities that the DIP is ready for delivery.

7.6.2.5

A

This aspect of OAIS is not currently modeled by Fedora. Fedora does not appear to use a staging area but serves requested content directly from the repository.

This aspect of OAIS is not currently modeled by Fez. Fez does not appear to use a staging area but serves requested content directly from the repository.

0




7.6.2.6

Storage retrieval - Demonstrate that Generate function accesses data objects in staging storage and applies the requested processes if special processing is required.

7.6.2.6

A

No staging storage area per se, but disseminators can process the master file(s), separating it from the DIP.

No staging storage area per se, and Fez architecture inhibits the disseminator functionality of Fedora.

1

Disseminator layer of Fedora is quite powerful and flexible, but cumbersome to configure in 2.2.3. Fez's inability to leverage the Fedora disseminators is a big downside.

7.6.3 Access - Deliver Response




A
















7.6.3.1

Web-accessibility - Demonstrate the display interface is web-accessible.

7.6.3.1

A

Fedora has a fairly limited web interface for retrieval.

Fez is entirely web-accessible.

2




7.6.3.2

Downloading - Demonstrate export function that provides XML output for batch downloads

7.6.3.2

A

Objects can be exported as METS packages, and some individual datastreams are downloadable as XML.

Fez can export some (but not all) metadata into XML. It cannot then re-ingest from the export output. Export is intended for spreadsheet manipulation of metadata.

1




7.6.3.3

Saving content - Demonstrate users are allowed to save digital content to a hard-drive, e-mail, and/or save search results.

7.6.3.3

A

Files may be downloaded. There does not appear to be a function for emailing or saving search results.

Files may be downloaded. There does not appear to be a function for emailing or saving search results.

1




7.6.3.5

System notification - Demonstrate a confirmation message is returned to the Coordinate Access Activities section after response has been sent.

7.6.3.5

A

This aspect of OAIS is not currently modeled by Fedora.

This aspect of OAIS is not currently modeled by Fez.

0




7.6.3.6

Audit trail - Demonstrate an audit trail of all actions is created and stored.

7.6.3.6

A

Tomcat logs can provide dissemination requests (according to Indiana Univ. DLP).

Fez can track downloads per file, but this is not working in testing.

1




7.6.3.4
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