» Data Dictionary

Post Categories

Draft 6.12.09

3rd Party Component: a reusable service, not developed or supplied by OLE, that fulfils an OLE library business process.

Acquire Entity: an OLE component whereby an entity is selected, obtained and the license/registry terms associated with the entity are documented; the entity is described and added to the collection.

Archive: governed by specific archival management policies, the process by which an entity or the copy of one can be stored or transferred to data storage.

Authenticate: process by which a system verifies the identity of a user. The user may be a person using a computer, a computer itself, or a computer program.

Authorize: process by which a system validates that a known individual or entity has the authority to perform specific actions within the system.

Business Process Engine: an OLE infrastructural middleware tool, the business process engine manages and executes library business processes defined by OLE

Business Process Modeling: a design approach used by OLE to document core library processes. The start and end points, step by step descriptions of how functions are performed, and contingencies are written down, and duplicate processes identified.

Capture: process by which exposed data/metadata from an agency/source is harvested or deposited into the collection

Collection: an OLE entity, a collection is a group of managed relationships. Collections are not necessarily formal library collections, and may be virtual collections, hierarchical relationships, relationships across formats, or a collection of people and services.

Commit Funds: process allows purchase price for entity to be encumbered from the appropriate fund; incorporates selector guidelines for assigning funds to order.

Component: a set of functional library business processes defined by OLE

Configure Metadata: process where metadata is normalized and processed according to established rules.

Create Entity Relationships: process that creates a link between two or more entities. Entities can include resources, people, courses, facilities, organizations, finances, etc.

Create Metadata: Process where descriptive, structural, and/or administrative information about an entity is generated.

Data Models: OLE infrastructural middleware tools, data models define how data is represented, accessed, and exchanged. Data models are independent of OLE components and databases.

Delete Entity Relationship: process that removes a link between two or more entities. Entities can include resources, people, courses, facilities, organizations, finances, etc.

Delete Metadata: process where descriptive, structural, and/or administrative information about an entity is removed

Deliver Entity: OLE component that tracks the request and supply of a resource including the resource availability, the terms of access, the preconditions of use, and whether the user requesting the resource has been identified and their credentials checked and verified.

Describe Entity: OLE component where metadata for an entity is obtained, created, modified and deleted

Discovery Tool(s): 3rd party components in OLE, discovery tools provide search and discovery functionality and may include features such as relevance ranking, spell checking, tagging, enhanced content, search facets. Discovery tools may be proprietary or open source.

Enterprise Level Integration: using a defined relationship, process by which a system allows linking of services and business entities across applications to promote unrestricted data sharing

Entity: OLE entities are resources, collections, persons, organizations, and services with separate identifies. Entities can be created, ingested, managed in relationships, described, and composed into a collection.

Event Manager: OLE middleware that analyzes and reports system event data, for example actions performed by users, changes in status.

Expose Metadata: process where metadata has been made available for capture

Identify Supplier: process that retrieves policy for contact with supplier and allows query of potential supplier list

Identify Terms of Use: process where a resource that has been requested has been checked for terms of access and preconditions of use.

Identify User: process where user requesting resource has been identified and their credentials checked and verified

Identity Management: process where user are identified and their credentials checked and verified. The users could be a person using a computer, the computer itself, or a computer program and could use protocols such as LDAP, Shibboleth, Secure Shell Keys, and Certificates. Identity management may be performed by an OLE or 3rd party component.

Inventory: process by which an entity is evaluated and tracked for retention and version preference, and access and descriptive metadata updated. May be used to manage weeding, reformatting, or relocation.

License: a right that gives a person or entity permission to do something that would be illegal if the person or entity did not have such permission. Usually the scope of the permission excludes ownership rights or privileges.

Manage Entity: OLE component that describes the processes that track the life-cycle of an entity including preservation, curation, evaluation, retention, relocation, duplication, version preference, rights management, binding, repair, reformat, replacement, and withdraw. Access and descriptive metadata may be normalized and updated in this process according to established rules.

Manage Entity Relationship: OLE component that allows for the creation, modification and deletion of relationships between any two or more entities. Entities can include resources, people, courses, facilities, organizations, finances, etc.

Manage Funds: process supported by the system to make payment for a service or product. Included in this process is a log trigger and log response; the system records the usage of services or product for audit, reporting or billing purposes.

Manage Inventory: process where entity is evaluated and tracked for retention and version preference, and access and descriptive metadata updated.

Manage Rights: process where information is maintained (collected, stored, updated) regarding rights of entities. Information is consulted and disseminated as necessary.

Manage User Relationship: an OLE or 3rd party component that describes processes to handle CRM (customer relationship management) including a user’s initiation for request of service to the fulfilling of that request.

Manage Terms of Acquisitions & Use: documents and manages acquisitions entities and associated information license terms (e-resources, gift, deposit, exchange, approval, etc.) selected for the collection; record is created with pending status; tracking begins as negotiations and/or evaluation of trial take place; final selection decision is recorded and pending status removed.

Metadata: ‘data about data,’ metadata defines, describes and manages information and may include descriptive, holdings, authority, financial, or other types of data.

Middleware: software that manages and connects OLE components and provides interoperability with 3rd party applications and components; consists of a number of functions which can be called upon by multiple components

Modify Entity Relationships: process that modifies a link between two or more entities. Entities can include resources, people, courses, facilities, organizations, finances, etc.

Modify Metadata: process where descriptive, structural, and/or administrative information about an entity is altered

Obtain Metadata: process where descriptive, structural, and/or administrative information about an entity is acquired.

Order Resource: obtain collection resources, with associated functions to manage providers. In the case of acquiring digital material it is a process whereby a system manages content in order to bring it into a collection.

Organization: an OLE entity, an organization is an administrative structure, for example a college or university, library, institution, society, consortium, or association.

Person: an OLE entity, a person is an individual represented in the environment. A few examples of persons include a user of a resource (such as a library user), a creator of a resource (such as an author), or a creator of metadata (such as a library staff member).

Pluggable Framework: OLE infrastructural middleware that allows separately installable software modules to interact seamlessly in the environment. This provides for increasing functionality of the system with components that are not built-in.

Policy/Business Rules: OLE infrastructural middleware, Policy/Business Rules modifies workflows based on locally defined policies

Preserve/Conserve Entity: process that tracks the preservation and curation of an entity that needs attention in regard to preservation/conservation activities including evaluation, binding, repair, reformat, replacement, and withdraw. Access and descriptive metadata may be updated in this process. Determine whether the item should be relocated to archives/special collections.

Process: a loosely coupled series of operations or activities that achieve a library business goal.

Receive Resource: process where a resource or service is received in response to request, for example an order request, a request for a service or resource, a gift.

Reference Model: provides an abstract view of how the environment functions and the relationships between the various components, entities, and middleware. The reference model provides a foundation upon which the architecture of the system, and the concrete details, will be built.

Reformat Resource: process where resource is selected, retrieved and converted; content is duplicated; access and descriptive metadata are updated.

Report Management: a 3rd party component to OLE that aids in the creating, viewing, and printing of reports. The software may provide an interface that will assist with the selection and extraction of data. This component may communicate with OLE through the report manager in the OLE middleware.

  • (e-Framework Service Genre: Report)

Report Manager: OLE infrastructural middleware reporting application that provides a connection between OLE, its data, and 3rd party report management software. The report manager may assist with the selection and extraction of data according to a particular type of report, as specified through the 3rd party report management software or through the policy/business rules middleware in OLE.

Repository: the OLE middleware which provides a registry of services. The repository manages the services to support their development, discovery, and use. Information about the services can be found here which could assist potential users with determining whether a service will meet their particular need, who maintains that service, etc.

Repository Management: an OLE 3rd party component that performs ingest, storage and basic integrity checks and preservation of entities stored in a repository.

Request Service: process where resource is requested from a resource provider or data source, or where a user initiates a request for service. The process will take into account whether the resource or service is available and can be requested by the user based on access and use policies.

Resource: an OLE entity, a resource is an item that may be collected and/or made available by an organization. Common examples of resources include books, journals, maps, websites.

Rights Management: process where information regarding rights of entities is collected, stored, and updated. For example, the license terms of an entity that is acquired are reviewed, approved, and retained. Rights information is consulted and disseminated as necessary, for example, a resource that has been requested is checked for terms of access and preconditions of use. Rights management may be performed by an OLE component or 3rd party component.

Rules Engine: See: Policy/Business Rules

Schedule Event: process that manages the scheduling of events based on policy implemented by the workflow engine. Provides check interval and deadline for certain actions such as claim, audit, renew, review, deliver.

Select Entity: describes the processes where metadata for an entity that has been selected for acquisition or trial, either permanently or temporarily, are created or obtained.

Service: a well-defined, reusable set of operations, services are independent software pieces that are the building blocks used to assemble library business processes in OLE.

Service Mediator: as part of the OLE middleware, the service mediator aids communication between system-level service consumers and service providers. As consumers request services, the mediator negotiates between the consumer and the provider to manage the service request and its delivery.

Service Oriented Architecture (SOA): the design approach that will be used to develop OLE, Service Oriented Architecture provides for loosely coupled, reusable services, and methods for allowing different applications to exchange data. By using SOA design architecture, OLE will describe a system that is can add new functionality and communicate with other systems.

Service Taxonomy: an index and classification of the services used in OLE. The taxonomy provides definitions of the services, helping to build a common and accepted language among OLE users.

Supply Entity: process where an appropriate entity is supplied subject to conditions or constraints on use.

Track Event: process that enables tracking the status of an event, a resource, a request, or a task are at any given point in the workflow.

Use Case: an example that illustrates the potential application of OLE, its components, and its processes. Use cases might be abstract or concrete. They help provide meaning to the functionalities of OLE.

Web Services: a software component that supports machine-to-machine transactions over a network, in particular, over the Internet.

Workflow: a series of activities that involve people, business processes, and software that achieve a library business goal.

Workflow Engine: See Business Process Engine.

Discussion

No comments for “Data Dictionary”

Post a comment