> > > >

While OLE has adopted functionality from the Kuali Financial System for acquiring print materials that includes placing orders, receiving orders, claiming orders, and paying for orders, acquiring electronic materials and tracking their life cycle has required additional interfaces and electronic documents.

In 1.0, initial development included the E-Resource Record and its associated maintenance documents. The E-Resource Record provides a place to store and view information about an electronic resource acquisition, including the title(s) involved and the content provider. Within the OLE user interface, the E-Resource Record presents a single, unified view of all information related to acquisition of an individual electronic resource or group of electronic resources, including titles, payment, licensing, administrative, and contact information.

E-resource acquisition requires the collection and storage of life cycle management data that is not part of the requisition or purchase order and lacks a home in most current systems. Long-term management of e-resources also requires the ability to view or link to related data from one coherent “place.” There is no eDoc that currently meets these needs. Therefore, we are defining a new type of record to handle e-resources.

Future releases will include a platform record to support electronic resource administration, full GOKb integration, workflow tools to support initial activation of access to electronic resources, alerts to help track the workflows, and enhanced abilities to create purchase orders that accurately link expenditures to electronic resources.

Because of the quantity of metadata that the E-Resource holds, the record contains a left-pane navigation bar.

The navigation bar includes:

E-Resource Navigation Descriptions

Tab Name

Description

Main

Displays the primary data elements and includes tabs for acquisitions, selection and access.

Instances

Users can manage the relationship between the E-Resource Record and OLE Instances and/or OLE E-Instances. In future releases, users will be able to import and manage data from GOKb

Purchase Orders

Displays and links to any purchase orders associated with an E-instance / Instance related to this E-Resource in 1.6. Also included at the top of the purchase order list is the sum of all payments for all purchase order line items linked to that E-Resource per fiscal year.

Invoices

Displays any invoices for any purchase orders associated with this E-Resource (see above).

Licenses

Displays license information from any License Requests an E-Resource Record is linked to. Users may also start a new License Request from this tab.

Event Log

Allows staff to store correspondence between libraries and publishers, vendors, etc. as well as notes about external activities. Some system-generated events are added automatically.

The E-Resource Record Main menu includes the Overview, Acquisitions, Selection, and Access tabs, in addition to the standard tabs.

The E-Resource Record Main menu contains a custom tab called the Overview that contains basic information about the E-Resource. The name of the E-Resource, Publisher, Platform and Vendor information as well as identifying information are noted here.

Overview Tab Definitions

Title

Description

Name

Required. The name of the E-Resource. Used also for searching.

Publisher

Record the name of the publisher of the E-Resource. In a future release, this will be linked to an Organization record.

Platform Provider

Display-only. The platform provider for the E-Resource. This is display only because it is based on the Platform(s) used by the E-instance(s) that are associated with this E-Resource.

Vendor Name

The name of the vendor. This is linked to a Vendor record in OLE.

OLE Identifier

Display only. Identifies the E-Resource within OLE.

ISBN/ISSNs

Display only. If the E-Resource Record has only one title, the subfield $a of the first ISBN/ISSN number from the record will display here.

GOKb Identifier

Display only. In a future release, for E-Resources imported from GOKb, this field will display the link to the GOKb interface.

Status

Current status of the E-Resource Record.

Status Date

Display only. Date at which the status was last updated.

The Acquisitions tab is used to document information about the nature of the resource being acquired and some of the purchasing information.

Acquisitions Tab Definitions

Title

Description

Material Type

Required. Defines the type(s) of material (i.e. journal, database) for reporting and managing different types of E-Resources. Select the Material Type from the drop down and click .

Format

Required. Defines the format(s) of the e-resource (i.e. electronic, print) for reporting and management. Select the format from the drop down and click .

Content Type

Required. Defines the type(s) of content included in the E-Resource (i.e. text, images) for reporting and management. Select the Content Type from the drop down and click .

Payment Type

Type of payment for the E-Resource. Examples may include free, paid, includes print, etc..

Package Type

Indicates the type of the package in GOKb. For example, locally negotiated or consortial package. In a future release, this will be imported from GOKb.

Breakable

Indicates whether individual titles that are part of the E-Resource can be canceled.

Estimated Price

The estimated price of the E-Resource used for reference. Once the Purchase Order exists, the estimated price will reflect the official price.

Description

Text field to allow staff to describe the E-Resource being purchased.

Order Type

Indicates the type of order, for example subscription or standing. In a future release, this will be used to populate Purchase Orders created for this E-Resource.

Package Scope

Scope of the E-Resource. For example, front file or back file. In a future release, this will be imported from GOKb.

Fixed Title List

Indicates whether an E-Resource is static (fixed) or has titles added/removed over time (not fixed).

Statistical Code

Select the Statistical Code from the drop down list. This is a custom local field to be used for reporting.

Fund

This field is meant to display the accounting information from Purchase Orders and Invoices. However in 1.6, the lookup will display the Vendor Reference Number.

Note

The bug has been documented and further coding is planned for 2.0. For more information, see OLE-4682

The Selection tab gives information about who has requested the E-Resource.

Selection Tab Definitions

Title

Description

Requester

The patron requesting the E-Resource. Enter a valid patron or search for them from the lookup and click .

Selector

The librarian requesting the E-Resource. Enter a valid OLE user or search for them from the lookup and click .

Requester/Selector Comment

Enter any patron or staff notes about the request and click .

Priority

Select a value from the drop down to assign a priority value to the request for purchase.

The Access tab describes the type of access and requirements for the E-Resource.

Access Tab Definitions

Title

Description

Type of Access

Select the type of access available for the E-Resource from the drop down. For example, site-wide or limited access.

Access Location

Select all of the locations that have access to the E-Resource from the list. Press shift+click or shift+arrow keys to select multiple options.

Authentication Type

Select the type of authentication needed to access the E-Resource from the drop down. For example, IP range or Shibboleth

No. of Simultaneous Users

Enter the number of simultaneous users allowed to have access the E-Resource at the same time, if there is a limit.

Technical Requirements

Enter additional notes about technical restrictions/requirements.

From the Instances menu staff can view and update the OLE Instances linked to the E-Resource. In a later release, staff will also be able to manage the relationship between the E-Resource Record and data imported from GOKb.

The Overview tab maintains the same information as the Main Menu's Overview tab.

Note

See the Main Menu Overview tab to review the Overview tab.

Users may set Default Coverage dates all E-instances that are associated with the E-Resource by clicking . A Coverage window will open. Enter the coverage information and click .

Users may set Default Perpetual Access dates for All E-instances that are associated with the E-Resource by clicking . A Perpetual Access window will open. Enter the perpetual access dates and click .

In this section, staff may also link a pre-existing OLE Instance/E-Instance to this E-Resource or create a new OLE Instance/E-Instance that is linked to this E-Resource.

  1. Click the button.

    A pop-up box with three options will appear.

  2. Choose from the options: Link to an existing instance, Create a new Instance for an existing bib, or Create a new bib and Instance.

Tip

Important : As of 1.6, you MUST click “save” on the Instances menu of the E-Resource before the link to an Instance or E-instance is actually saved.

The Instance Details tab shows a table listed of all instance (print or electronic) that have been linked to this E-Resource. Multiple instance from a single bib can be linked to the same E-Resource. To unlink a specific instance, simply click the Remove button next to it.

The Event Log menu is available to store the correspondence between librarians and publishers, vendors, and others. Libraries may also use the Event Log to record an audit trail of changes made to the E-Resource Record or events that took place outside of OLE.

The Event Log tab captures certain types of automated entries for E-Resources, such as a change in status. Users can also manually add entries to capture external communications, notes, or to summarize any actions external to OLE (such as with Vendor/Provider, University Legal, University Purchasing, etc.). You may add an event by filling out the required fields and clicking . Users with appropriate permissions may also delete an entry from the Event Log by clicking

Many events can be recorded in the event log. You may display 10, 25, 50, or 100 entries at one time. Additionally, you may search for events from the search bar.

Event Log tab Definitions

Title

Description

Type

System generated. The event type value will be ‘system’ when the request is initiated, 'user' if a line was added manually by user; 'file' if an Agreement doc was added; 'agreement' if a linked Agreement document was edited or added; 'location' if a location change occurred; 'status' if a license status change occurred.

Event Date

System generated. Logs the date for the event log line item.

User

Required. Logs the user id of the person associated with the event log change. Defaults to current user but can be modified by entering a name or searching from the lookup

Note

Required; may be manually added or system generated. Users may input information to provide audit trail information. System also records what events have occurred.

  1. Select E-Resource from the Select/Acquire Menu.

  2. To create the E-Resource, fill in data in the required fields: Name, Status, Material Type, Content Type and Format.

  3. Enter additional information and click .

  4. From this point the E-Resource acquisition process is non-linear. Four different workflows may be set in motion in any sequence. Each of these workflows can be started from a related menu page on the E-Resource; the status of the related workflows are intended to display in the Workflows tab of the Main menu of the E-Resource.

  5. In addition, the E-Resource Record has its own locally configurable workflow. As the E-Resource Record is passed through each approval in the local workflow, the document is editable for staff with appropriate permissions to add or modify as necessary.

  6. To start the local workflow for the E-Resource, click . The document will route to the Action List of the first user or group in the local workflow.

  7. Once that workflow step has been completed, the appropriate user will click to move the document to the next approver.

loading table of contents...