Functional Requirements of DC-Lib AP for Bibliographic Text Resources
According to Singapore Framework the Functional Requirements describe the functions of an application with regard to the user needs. A similar statement we find at the Functional Requirements for Bibliographic Records (FRBR) which define the following four generic user tasks:
-
find an entity
-
identify an entity
-
select an entity
-
acquire or obtain an entity
In addition to these generic functionalities the DC Lib AP for Bibliographic Text Resources defines the following use cases as the specific functions this profile has to achieve:
Metadata as linked data
-
Use Case: Metadata describing bibliographic text resources shall be used in a linked data context.
Requirements: Use a linked data compatible syntax.
Use Case: Metadata describing bibliographic text resources shall be combined with metadata from other sources.
Requirement: Use a domain model which allows to join data from other domains.
Use Case: Metadata describing bibliographic text resource shall be used to fix the relationships between these and other resources.
Requirement: Use metadata terms supporting the usage of identifiers for citation and linking.
Simple creation of bibliographic metadata
-
Use Case: A developer wants the simple and easy implementation of a cataloguing application.
Requirement: Use a domain model as simple as possible.
Use Case: A metadata provider wants to make specific assertions about his copy of a publication.
Requirement: The domain model has to distinguish between a publication and its local copies.
Use Case: A metadata provider wants the creation of metadata quickly and efficiently.
Requirement: Support a standard description using a
small number of mandatory metadata terms combined with a manageable
number of optional terms.
Use Case: A metadata provider wants to describe bibliographic text resources by non-librarian staff.
Requirement: Support the creation of metadata by using plain and well defined metadata terms.
Discovery of library resources
-
Use Case: A user searches for a particular publication
of a work and knows the titel, persons and/or coporation responsible
for it and/or the identifier.
Requirement: Support the search of a particular publication by given titles, names (of a person or corporate body) and/or identifiers.
Use Case: A user searches for all publications of a given person or coporate body.
Requirement: Support the search of all publications for which a given person or coporate body is responsible.
Use Case: A user searches for informations about a specific topic.
Requirement: Support the search of all publications of a given topic.
Use Case: A User wants to filter search results.
Requirement: Support the filtering of search results
by languages, formats, dates, names (of persons or coporate bodys),
subjects, types of work and availabilities.
Use Case: A user wants to identify relevant publications.
Requriement: Support the identification of the
relevance of a publication using titles, persons or coproate bodies
responsible for the work, descriptions, dates, languages, subjects,
relations and identifiers.
Use Case: A user wants to get information about the life cycle of a particular publication.
Requirement: Show the different dates of the life cycle of a particular publication.
Use Case: A user wants to know what relationships exist between different publications.
Requirement: Show the relations between publications and link one to another by these relations.
Use Case: A user wants to identify all copies of a publication he can use.
Requirement: Show the usability of a copy by the availiabilities and access conditions.
Use Case: A user wants to obtain a specific copy.
Requirement: Show the identifier and the availability and access conditions of a particular copy.
Back to RevisionDraft