Data Catalog Collection
Collections
- A collection is a group of specifications related by topic or purpose.
- Collections are reviewed and approved using a separate workflow approval process.
- The permissions for working with collections are managed by the specification permissions.
- Specification editors and managers create collections and are typically assigned to steps in the approval process.
- Options for creating and browsing collections, such as the Collections Queue, are located under the Specifications menu.
Attributes of a Collection
- The purpose explains why the collection exists.
- The purpose may include information about business decisions informed by the collection or who uses the collection and how often.
- The description provides a brief explanation of the characteristics of the collection, such as “this is a collection of all the monthly reports that the admissions office prepares for the Dean of Admissions”.
- The description may contain links to specific specifications included in the collection.
- The owner is the person or office you should contact if you have questions about the collection's contents.
- The owner is not necessarily the same individual who created the collection in the Data Cookbook.
Functional Details
- The Functional Details provide information not captured in the Purpose or the Description (found on the Overview tab) and lists the related specifications.
Technical Details
- Provide details about the technical aspects of this collection.
- These details might include how the collection is configured; specific access requirements for running the related specifications; or technologies used to create and maintain the specifications.
- Functional areas categorize objects by topic or business area and
- Determine the workflow assigned to the object
- Control permissions for viewing, editing, and managing the object
- Provide an option for filtering on the object's Browse page
- Editors can add or remove functional areas for an in-progress or approved version of an object. However, changing the functional areas may change the workflow and, for items currently in progress, may result in the approval process starting over.
- Related specifications are those specifications that are part of this collection.
- Collection editors can relate a specification by reference, like a WikiLink, in the Purpose or Description (Overview tab) or Narrative (Functionality tab) and those specifications will be displayed here. Collection editors can also add or remove related specifications from the sidebar.
- To reference a specification using a WikiLink, use the syntax [[spec:]] where the name is spelled exactly as it is in the Cookbook.
- Referenced definitions are those definitions that are either referenced, as a WikiLink, in the Purpose or Description (Overview tab) or Narrative (Functionality tab) or added through the sidebar panel.
- Collection editors can also add or remove referenced definitions from the sidebar.
- To reference a definition using a WikiLink, use the syntax [[def: is the name of the definition, spelled exactly as it is in the Cookbook.
- Referenced source data systems are those systems that are relevant to this collection.
- These data systems are either mentioned, as a WikiLink, in the Purpose or Description (Overview tab) or Narrative (Functionality tab) or added through the sidebar panel.
- To reference a data system using a WikiLink, use the syntax [[data: is the name of your data system.
- Tools are the applications or other methods used for creating the different specifications in this collection.
- Examples might include Sigma Computing, Argos, and Cognos.
- Tags are searchable words or phrases that can be created once and shared by multiple definitions, specifications, or collections. They are used as a filter on the object's Browse page.
- Example tags include:
- Bio/Demo
- FERPA
- Training item
- Editors can add or remove tags for an approved or in-progress definition or specification (or collection in the Enterprise Edition).
- Attachments are files added to an object to provide information not covered in the standard Cookbook fields. These files are added to a specific version of the object.
- Editors can add attachments, such as a text file, a PDF, even a graphic or picture, that might help explain that object. All users who can view the object can view its attachments.
Tags
None found.
Last updated: July 29, 2025
Contact
Team Name
Business Intelligence and Web Services
Office Location
Burke Library
198 College Hill Road
Clinton, NY 13323
198 College Hill Road
Clinton, NY 13323
Phone
Email
