Supply Entity

 

 

Process Module:  Deliver Entity

Process Title:  Supply Entity

Definition:  Supply Entity describes the process where an appropriate entity is supplied to a valid requestor subject to conditions or constraints on use. Restrictions on use may be actively enforced by software applications, for example the ability to read, download, print; number of simultaneous users; a time limit; payment of a fee or royalty. Conditions may be determined by copyright, set by the author or by the rights holder.

Workflow / Process Diagrams:

 

Use Cases: Entity can be retrieved from the library for check-out onsite or delivered to another location (library, office, desktop, off-campus site).   Entity may be supplied by the local library, a consortial library, another institution, or a document supplier.  Entity is delivered with conditions of use, for example it must be returned within a specified timeframe, the resource must be used in the library, the resource may not be duplicated, or there is a fee associated with use of the resource.

This applies to print and electronic.  Both returnables and consumables.  May be local, consortial, purchased on demand or external to institutional ownership.  Can be an original or a copy.

Reference(s)

  1. (NLA Services Framework 1.1: Authenticate)  Verify whether an identity claim made by an individual or entity (the principal) is true.  The principal may be a person using a computer, a computer itself or a computer program.
  2. (NLA Services Framework 1.2: Authorise)  Establish if an authenticated principal is permitted to perform a specific operation based on policy
  3. (NLA Services Framework 6.10: Supply)  Supply an appropriate copy of a resource once conditions have been met
  4. (NLA Services Framework 7.9: Request) Lodge a request for a wanted resource with a resource provider, taking into account availability, access and use policies and any conditions and obligations these impose on the requester (Service Usage Model)
  5. (e-Framework Service Genre: Authenticate) Describes authentication, the process of uniquely identifying an individual or entity (the principal) based on objects provided for verification (credentials). Credentials should be difficult to falsify or forge, either by keeping them secret or by making them difficult to replicate. Authentication seeks to ensure that the principal is who they claim to be. The degree of certainty varies according to implementation and business context.  Authentication typically verifies the principal’s association with an electronic identifier. Authentication may also determine that the principal has certain attributes or is a member of specified or predetermined groups.  In security systems, authentication is distinct from authorisation, which is the process of establishing what a principal is permitted to do, their access rights to system objects based on their identity.
  6. (e-Framework Service Genre: Authorise) Process of establishing what a principal is permitted to do. Authorisation typically occurs after Authentication so that the principal can be identified. Authorisation may also use a principal’s attributes, information about what the principal is intending to do (the target), and environment information to make authorisation decisions.
  7. (CollectionSpace Functional Requirements: Loans and Dispatch)
    • Loans In
      Managing and documenting the borrowing of objects for which the organization is responsible for a specific period of time and for a specified purpose, normally exhibition/display, but including research, conservation, education or photography/publication.
    • Loans Out
      Documenting and managing the loan of objects to other organizations or individuals for a specific period of time and for a specific purpose, normally exhibition/display, but including research, conservation, photography and education.