Kuali OLE

Process Module: Acquire Entity

Process Title: Receive Resource

Definition: Describes the process of receiving, describing and paying for an entity that fulfills an order request.  

Workflow/Process Diagrams:

Use Cases: Search system for order record.  Confirm that the acquired entity fulfills the order request in the system.  Obtain metadata for the entity if it is not already in the system. Logging receipt of an item in the system triggers the invoice payment/manage funds processes.

Reference(s):

1. (NLA Services Framework 5.1: Add) Put a new business object into a collection
2. (NLA Services Framework 6.5: Describe) Process whereby resources in a collection, or that are in the process of being selected and acquired, are described. The metadata may be entered in real-time or harvested from or deposited by another agency. The description may evolve over time, as material is identified for selection, acquired, accessioned, annotated, curated and used.
3. (e-Framework, Service Genre – Add) describes the insertions of objects into collections of like objects. This MAY also include the metadata associated with an object. An ICT architecture that offers a service of the Add genre will be able to support remote updates of items within their collections.
   Add implementations will typically also offer the users the functionality to update and delete existing objects within collections. Typical implementations assign a unique identifier to objects within their collections, and also persist data in some form until it is explicitly removed. However, it is not inconceivable that other processes could consume added data very rapidly; or that a collection would be deleted at the end of a session.
   As defined the Add Service Genre is not access controlled. Any client may attempt to contact an Add service end point. There are no authentication controls. The service end point is responsible for determining which clients can Add content.
4. (e-Framework, Service Genre – Generate Metadata) The generate metadata  service genre defines how to generate a metadata object, encoded in an XML document, containing basic cataloging and descriptive metadata for/from a content object.  The metadata object SHALL conform to an identified metadata standard.  This service genre is applied to a content object which SHALL conform to an identified content object standard.
5. (CollectionSpace: Cataloging Requirements) The compilation and maintenance of key information, formally identifying and describing objects. It may include information concerning the provenance of objects and also collections management documentation e.g. details of acquisition, conservation, exhibition and loan history, and location history. It need not bring together in one location everything known about an object, but should provide cross references to any other relevant information source known to the organisation.