Version History

To cite the latest version of this work use http://resolver.net.au/hdl/102.100.272/CF9NKCNQH

To cite this version of this work, use http://resolver.net.au/hdl/102.100.272/CF9NKCNQH

1 Purpose

This user manual is intended to give users a better understanding of the PILIN FRBR (Functional Requirements for Bibliographic Records) Tool.

2 Background

The PILIN project has been set up to explore identifier use not only in the narrow context of identifying concrete objects, but also in various value-added services. Such services enhance existing processes outside the domain of identifier systems, through the use of persistent identifier services. One of the priority value-added services identified by the PILIN project is using identifiers to represent and interrogate the information model for a domain. Persistent identifiers can identify not only the concrete data objects of a domain, but also the abstract concepts used to model how those concrete objects are related to each other.

To illustrate such use of identifiers in information modelling, PILIN has developed this tool for creating and updating identifiers specific to a particular information model. The tool creates structures for representing the relations between conceptual units in the information model; these are ultimately used to represent relations between concrete objects according to this model.

Because the conceptual units are identified by persistent identifiers, the relational structures represented are expressed as relations between persistent identifiers. In the particular information model used, concrete objects are represented only as URLs; this conforms to PILIN’s determination that persistent identifiers cannot be used outside of an (implicit or explicit) information model, and identify constructs of the information model rather than object instances.

This tool uses the FRBR model of bibliographical entities as its base information model. Although FRBR has broad applicability, its use in this tool is intended only as illustrative: other information models can be supported by persistent identifiers, and persistent identifier management tools can be adapted to operate with different information models.

FRBR is a standard developed by the International Federation of Library Associations and Institutions (IFLA), modelling the entities involved in library catalogues and databases, and how users interact with them. FRBR has also proved quite useful in modelling the relations between items in digital repositories. The standard is available at: http://www.ifla.org/VII/s13/frbr/frbr.htm

3 Introduction

This is a tool for creating and maintaining identifiers related to each other through the FRBR information model. This information model relates objects which belong to the same intellectual work but differ in content or presentation.

The relationship is modelled through a hierarchy of four levels of abstraction:

A Work is the abstraction under which all the related objects are grouped.

Different Expressions of the Work differ in content, but are still considered to belong to the same abstract Work. Examples include drafts, versions, and translations.

Different Manifestations of an Expression share the same content, but differ in how they present it.

An Item is a concrete object. If an item belongs to a work, it must belong to a particular manifestation, which in turn belongs to a particular expression of the work. Items in the PILIN realisation of FRBR are identified only as URLs and do not have their own persistent identifier.

This means that expressions, manifestations, and items form a hierarchy, which allows the relation between individual items to be represented as a tree. The FRBR model is intended to capture the possible relations between individual items, through the intermediate abstract entities it invokes.

The FRBR tool can be used to manage, navigate, and resolve Handle identifiers which realise the FRBR information model.

4 Add FRBR Entity

This section allows the user to add a new FRBR entity to the system. Handles for the FRBR entities are created which are related to each other through the FRBR model.

The user can

• Add a complete sequence of related Work, Expression and Manifestation in a single operation.

• Add only a FRBR Work. The related Expression and Manifestation can be added later.

• Append an Expression and Manifestation to a previously created Work.

• Append only an Expression to a previously created Work.

• Add only a Manifestation(s) for a previously created Expression, under a previously created Work.

4.1 Handle Server Authentication.

The first page that the user sees is the Handle server Authentication page. The page requires us to nominate and authenticate the user as an administrator for the Handle Server that we are going to log into.

The G.H.R. (Global Handle Registry) maintains the list of all the L.H.S. (Local Handle Servers) which are registered for use. The Handle system uses P.K.I. (Public Key Infrastructure) as its authentication model.

While setting up an L.H.S., a private key is generated that is used to authenticate the administrator for the L.H.S. After providing this key we are authenticated to perform the required operations on the L.H.S.

A pass phrase may have been used to encrypt the private key while the L.H.S. was set up. The same pass phrase, if any, is again required for authentication.

4.2 Add FRBR Entity.

Users here can add a new FRBR entity to the system, as explained above. This may involve creating a new work, or appending entities to an existing Work.

After the authentication is successful, the user sees the Handle operations page, which says which L.H.S. will be accessed. The Handle server namespace can be changed to a different L.H.S. by pressing the “Change” button on the screen.

The user can select from the two options available:

• Create a new FRBR Work.

• Append Expression/Manifestation to an existing Work.

Click “Next” button to proceed.

4.2.1 Create FRBR Work.

At this page the user can

• Create a complete Work, including a Manifestation and an Expression corresponding to the work.

• Create a Work and its Expression (with no Manifestation).

• Create just a Work (with no Expression or Manifestation).

Work Title (mandatory) is the title of the identified work.

Work Description (optional) is a text describing what is distinctive about the particular Work.

Expression Version (mandatory if Expression is created, optional if only Work is created) is a version name identifying the particular Expression for a particular Work.

Expression Description (optional) is a text describing this particular Expression version.

Expression Creation Date (mandatory if Expression is created, optional if only Work is created) is the date of creation of the particular Expression. This defaults to the current date, but it should contain the date when the Expression (version of the document) was created. This is distinct from the date when the Handle for the Expression is being created (i.e. now).

Manifestation Format (mandatory if Manifestation is created, optional if only Work or Work + Expression are created). The format for the Manifestation; only a few options are allowed. ?? – not sure what this means?

Manifestation Description (optional) is a text describing this particular Manifestation.

Manifestation URL (optional) is the item in an FRBR model. This is an actual instance of the resource being identified. A Manifestation can have more than one Item, meaning that the file with that format can be stored in multiple locations.

An example of how to fill out these fields is:

• Work Title: A Report On PILIN and FRBR.

• Work Description: A preliminary report on how the PILIN project has used the FRBR model in its information modelling.

• Expression Version: 0.2.

• Expression Description: Initial draft for discussion

• Expression Creation Date: 2005-10-07

• Manifestation Format: PDF

• Manifestation Description: PDF version, password-protected.

• Manifestation URL: http://example.com/a.pdf ; http://example.org/sample/a1.pdf

The “Add a new URL” button is used to add another Item to the Manifestation.

The “Delete” button can be used to delete the individual Item.

Click on the “Next” button to proceed with creating the F.R.B.R. Entity.

4.2.2 Add FRBR Work Result.

After the successful creation of the FRBR Entity, the user is shown the Navigation view of the newly created FRBR Entity. The user can also add more Expressions and Manifestations to the Work here.

This page shows the created Work, related Expression(s) and Manifestation(s).The lowest level of FRBR Entity created is highlighted.

NOTE: A link “FRBR Activity Log” appears on the left frame after the creation of the FRBR Entity. The user can open or save this log file to view the Handles created in the session.

NOTE: The “Add a new Expression” button can be used to add another Expression for the current FRBR Work.

NOTE: The “view all expressions” button will display all the Expressions for the current FRBR Work.

NOTE: The Expression version string is a link: clicking it will display details for that Expression, along with all its Manifestations.

4.2.2.1 Add a new Expression

The user can add another Expression for the current FRBR Work here. Work fields are disabled, and are provided as a visual reference to where the Expression is being added.

As with Create FRBR Work, users can create a Manifestation corresponding to the Expression at the same time.

4.2.2.2 View All Expressions

This button is used to view all the Expressions under a given FRBR Work.

Individual expressions are links that resolve to a random manifestation for that Expression.

5 Navigate Tree

This section of the FRBR Tool is used to navigate the hierarchy for any FRBR Entity. Navigation can be done either through the FRBR ID for the entity, or the FRBR Work title. The request matches the Entity corresponding to that input, and displays the Entity in a structure suited for exploring the relations between entities in the system.

If the FRBR Work title is entered for the navigation, the results displayed include all possible matches as hyperlinks.

The relations between entities are explored as described in Section 4.

6 FRBR Resolver

This section resolves the FRBR identifier for any FRBR entity to an Item corresponding to the most recent Expression. The choice of Manifestation and Item is random.

This functionality allows us to resolve an identifier for an abstract work to a presentation of the most recent version of the work. This enhances the default resolution of a Handle, by having it take into account the FRBR relations between the entities involved.

The user can enter the FRBR ID and click the “Resolve” button to view the URL of an Item. The user can then click the URL to access the actual item belonging to the most recent Expression.

7 Appendix of FRBR Custom Types