» Scope Document Glossary

This Glossary supports language used in the scope document.  As with the scope document, this glossary is in the early stages of development and will be revised and extended over time.   We are sharing the document now with the understanding that some elements may change as result of further discussion.  Please use the feedback mechanism to add comments.

Campus  

  • Institutional research unit  (e.g. Google campus, college campus) 

Community 

  • Community of interest; e.g., the library community, the vendor community
  • The group of institutions which will come together to govern and help to sustain the software emerging from the OLE project

Data Governance 

  • Provides for overall data management that includes policy setting and compliance enforcement, usability, availability, integrity, and security of an organization’s data 

Institution 

  • The organization within which a research library might reside (which might be the library itself)
  • Any not-for-profit organization that may become a stakeholder in the project 

Reference Implementation 

  • A production-quality (i.e., usable) software implementation of the design created through the OLE process, which encompasses all of the specified functions of the system 
  • To obtain Mellon support for construction of the software, the reference implementation must be open source 

Research Library 

  • A library which has as a primary mission the support of research; typically, a college, university, or national library

Identity Management

  • One portion of the process of ensuring that individuals’ access to institutional resources complies with law, regulation, and institutional policy (the other two portions are: authentication, the confirmation of identity at some particular moment, e.g., through login; and authorization, the granting/denying of permission to perform certain activities on certain data at a certain time). Common functions include provisioning: the establishment of an account for an individual, with associated metadata, such as password and institutional role, that are needed for authentication of identity and authorization of activity, respectively; group management, which facilitates the process of assigning individuals to groups for the purposes of granting shared permissions; updating, which includes safeguards restricting access to the individual’s record to authorized persons; reporting, also compliant with identity-protection policies; and deprovisioning.
  • A class of software that facilitates effective identity management; open source examples include the Shibboleth, Central Authentication System (CAS), and OpenID.

User 

  • Any person who may interact directly with the system, including patrons, staff members, or others.

 

 

Discussion

No comments for “Scope Document Glossary”

Post a comment

Close
E-mail It