Difference between revisions of "Basic Tables"

From CollectiveAccess Documentation
Jump to: navigation, search
(Created page with "=== Basic Tables === #Lots #Objects #Entities #Collections #Events #Works #Loans === Lots === Lots represent an accession or acquisition of one or more assets. The details a...")
 
Line 1: Line 1:
=== Basic Tables ===
 
#Lots
 
#Objects
 
#Entities
 
#Collections
 
#Events
 
#Works
 
#Loans
 
 
 
=== Lots ===  
 
=== Lots ===  
 
Lots represent an accession or acquisition of one or more assets. The details and terms of a gift, purchase, loan, long-term loan, or bequest are recorded here. Registration information includes a Lot Identifier, Description, Accession Status, and Extent, as well as any other pertinent relationship information.  
 
Lots represent an accession or acquisition of one or more assets. The details and terms of a gift, purchase, loan, long-term loan, or bequest are recorded here. Registration information includes a Lot Identifier, Description, Accession Status, and Extent, as well as any other pertinent relationship information.  

Revision as of 18:52, 3 October 2012

Lots

Lots represent an accession or acquisition of one or more assets. The details and terms of a gift, purchase, loan, long-term loan, or bequest are recorded here. Registration information includes a Lot Identifier, Description, Accession Status, and Extent, as well as any other pertinent relationship information.

Objects

Object records represent the assets of a collection, typically the physical or born-digital items you are managing. For BAM, Objects will include documents (such as correspondence, production records, ephemera, etc.), born-digital and other media (audio, photographs, video) and the more open-ended category "other non-textual material." Objects will comprise the bulk of your cataloging work.

Entities

Entity records represent the authority for specific people or organizations. These can be creators, artists, donors, publishers, performers, or a person or group involved in some way with the BAM collection.

Collections

Collections contain a defined group of objects. Collections can represent physical collections, symbolic collections of items associated by some criteria, or any other arbitrary grouping. One such example would be the BAM Programs and Playbills collection, which, as the title indicates, holds all of the programs and playbills dating from 1857 to the present. BAM’s Collections will be described using DACS; “Describing Archives: A Content Standard,” which is a Society of American Archivists Standard. Please refer to the content standard when titling and describing a new Collection record. Once a Collection has been catalogued in the database, it can become the “hierarchical parent” of an object which can help to narrow and define access to the item.

Events

Events are productions or happenings that have occurred during BAM’s history. The record for an Event (or production) is distinct from that for a "Work" in that it describes a performance, whereas a "Work" is the actual play, text, choreography, etc. that is being used for a particular event.

Works

As mentioned above, Works are the plays, texts, etc. that are being performed in a production (Event). Thus, Hamlet, the play itself, would be a Work, while a certain production of Hamlet would be an Event.

Loans

Loans are used to track objects that are on loan to or from other institutions. Navigating to New > Loan in or out will allow you to create a new loan, entering in contact information and other important details. Objects are attached to loans in the same manner as collections, events and entities.

Namespaces

Variants
Actions
Navigation
Tools
User
Personal tools