Functionality-oriented Criteria

Functionality-oriented Criteria

The following criteria have been selected to verify whether or not the ‘digital library’ conforms to the Digital Library Reference Model from the Functionality domain point of view.

Regardless of the type of Functionality a ‘digital library’ is conceived for, it meets at least the following criteria:
The Digital Library must offer a clearly identified set of Functions and this can not be an empty set.
» The purpose of the DL is to offer functions, i.e., a particular processing task that can be realised on a Resource        or a Resource Set as the result of an Action of a particular Actor.
» Every Function must have (identifiedBy) a unique identifier (Resource Identifier).
A Function is a Resource, thus it must be identified by a persistent identifier if it is to be distinguished from    other Functions managed by the DL.
» Every Function must be performed (perform) by Actors.
DL Functions are the implementations of functions and services enabling Actors to interact with the DL.
» Every Actor must be provided with (perform) Functions to Access Resources.
The DL must implement functions to enable actors to access, e.g., discover, acquire and visualize, all types of Resources (Information Objects, Actors Profiles).
» Every Actor must be provided with (perform) Functions to Discover Resources.
Actors must be able to find the desired Information Objects, search and access not only the DL Content, but also other Actors or Functions.
» Every DL System Administrator must be provided with (perform) Functions to Manage & Configure DLS.
DL must implement functions for handling the DLS and configuring its settings.

Additionally, a Digital Library should meet the following criteria:

  • Every Function should be able to interact with (intertactWith) other Functions.

DL functions should exchange information with other functions regulating their behaviour and performance.

  • Functions to Acquire (actOn) Resources should be provided.

DL functionality should enable Actors to retain Resources e.g., Information Objects and Actor Profiles, in existence past their interaction with the Digital Library System.

  • Functions to Browse (actOn) the Resources should be provided.

DL should implement services enabling Actors (virtual or real) to browse the available DL content, user profiles, policies, etc.

  • Functions to Search (actOn) the Resources should be provided.

Actors should be able to look for specific objects held within the DL by expressing queries and by entering specific keywords and constraints.

  • Functions to Visualize (actOn) the Actor’s requested Resources should be provided.

A DL should deliver to Actor the requested information using the appropriate visualizations to produce comprehensive and well-presented objects, lists and query result sets.

  • Functions to Manage Information Object(s) (actOn) should be provided.

A DL should implement functions to handle, i.e., disseminate, publish, process, analyze and transform, the Content of the DL, i.e., Information Objects.

  • Functions to Manage Actor(s) (actOn) should be provided.

A DL should implement Functions to establish registered actors, personalize their preference and apply user profiles.

  • Functions to Manage DL specific domains in a large scale should be provided.

The DL should implement services and mechanisms to handle DL domains as a whole, e.g., Manage (import, export) all the Content of DL rather than handling each Information Object individually.

Finally, a Digital Library may meet the following criteria:

  • Functions may depend on (influencedBy) the Actor’s Profile who invokes them.
  • DL Functions that are offered to the Actor(s) may be customized according to his/her profile, DLS role and rights and /or personal preferences.
  • Functions may consist of other parts (hasPart), i.e., sub-functions.
  • Functions may be organized in arbitrarily complex workflows, based on composition and linking facilities.
  • Functions may be enriched with Metadata (hasMetadata) and Annotation (hasAnnotation).
  • DL Functions may have a description, which tells what the function does and how a system or human can interact with it.
  • Functions may enable (actOn) Actors (virtual or real) to Collaborate with each other.
  • Actors (virtual or real) may act as peers who are able to communicate, share and exchange information collaboratively.