CollectiveAccess - Recent changes [en]

Intrinsic Bundles

2010-09-07T23:16:45Z

Primary Types

2010-09-07T22:18:56Z

Intrinsic Bundles

2010-09-07T22:14:10Z

Created page with 'The bundle names for various intrinsic database fields are the field names themselves. Bundle names for other user interface elements are listed in the following tables. ==For O…'

New page

The bundle names for various intrinsic database fields are the field names themselves. Bundle names for other user interface elements are listed in the following tables.

==For Object (ca_objects)==
{|border="1" cellspacing="0" cellpadding="5"
|-
||'''Bundle Name'''||'''Description'''
|-
||preferred_labels||Fields for setting object preferred title
|-
||non_preferred_labels||Fields for setting object non-preferred (alternate) titles
|-
||idno||Object identifier field (often used for current accession number).
|-
||locale_id||Object record locale drop-down
|-
||item_status_id||Object status value based upon values in object_statuses list
|-
||acquisition_type_id||Object acquisition value based upon values object_acq_types list
|-
||source_id||Object source value based upon values object_sources list
|-
||extent||Numeric extent
|-
||extent_units||Units of extent
|-
||access||Control of public access using values defined in the access_statuses list
|-
||status||Indication of current workflow status as defined in the workflow_statuses list
|-
||ca_object_representations||Adds controls for adding, updating removing and viewing linked media
|-
||ca_objects||Adds controls for linking to other objects
|-
||ca_entities||Adds controls for linking objects to entities
|-
||ca_places||Adds controls for linking objects to places
|-
||ca_occurrences||Adds controls for linking objects to occurrences
|-
||ca_collections||Adds controls for linking objects to collections
|-
||ca_storage_locations||Adds controls for linking objects to storage location hierarchy
|-
||ca_object_lots||Adds controls for linking object to lot
|-
||ca_object_events||Adds controls for creating and managing object event records
|-
||ca_list_items||Adds controls for linking terms in controlled vocabulary lists to objects
|-
||ca_sets||Adds controls for adding and removing object from sets
|-
||hierarchy_navigation||Adds user interface display for hierarchy object is part of
|-
||hierarchy_location||Adds user interface to change location of object in a hierarchy of objects.
|-
|}

==For lots (ca_object_lots)==
place holder

==For entities (ca_entities)==
place holder

==For places (ca_places)==
place holder

==For occurrences (ca_occurrences)==
place holder

==For collections (ca_collections)==
place holder

==For storage locations (ca_storage_locations)==
place holder

==For object representations (ca_object_representations)==
place holder

==For lists (ca_lists)==
place holder

==For list items (ca_list_items)==
place holder

==For sets (ca_sets)==
place holder

==For set items (ca_set_items)==
place holder

==For object events (ca_object_events)==
place holder

==For lot events (ca_object_lot_events)==
place holder

Building Installation Profiles

2010-09-07T21:54:58Z

← Older revision		Revision as of 21:54, 7 September 2010
Line 179:		Line 179:

	Once control lists are defined, they can be used in Metadata Element Set (Attribute) Definitions to create drop-down menus.		Once control lists are defined, they can be used in Metadata Element Set (Attribute) Definitions to create drop-down menus.
		+
		+	===Metadata Element Set (Attribute) Definitions===
		+	Metadata element set definitions (element sets) are templates for the various data entry units in the cataloging interface. Element sets can define something as simple as a text field or as complicated as a repeating multiline form with text fields, date fields, measurements, drop-down lists and more. Thus the “sets” moniker – a single data entry unit can be composed of any number of basic attribute types (see http://wiki.collectiveaccess.org/index.php?title=AttributeTypes for a full list).
		+
		+	Before we go further, some terminology should be defined. A metadata element set is a collection of metadata elements that defines a single editable unit of metadata. Each element is a single value of some specific type – some text, a number, a date, a measurement, a point on a map, etc. Thus, an element set is a collection of values.
		+
		+	An element set does <b>not</b> represent data. Rather, it defines the structure of data you may create during cataloguing. An attribute is data structured according to an element set. Thus, you are not creating element sets when cataloguing. Rather, you are creating attributes patterned after some element set.
		+
		+	Element sets are highly configurable and key to creating custom systems. While standards are in general a very good thing, our experiences working with partner institutions have shown that successful systems need to be flexible and extensible. Every collection is different and just about every cataloging project has at least a few unique requirements. A configurable system permits strict adherence to standards or customization based on the needs of the project. While this may seem a little confusing at first, it actually gives you much more control of exactly what kind of data you would like to capture and how you would like it to display.
		+
		+	No specific element sets are required. You need only specify those that you need for your system; however there are a number of components that comprise an element set definition.
		+
		+	A basic element set looks like this:
		+	<code><pre>
		+	description = {
		+	datatype = Text,
		+	preferred_labels = {
		+	en_US = {
		+	name = Description,
		+	description = An account of the resource.
		+	}
		+	},
		+	settings = {
		+	fieldWidth = 80,
		+	fieldHeight = 5,
		+	minChars = 0,
		+	maxChars = 65535
		+	},
		+	documentation_url = http://dublincore.org/documents/dcmi-terms/#terms-description,
		+
		+	type_restrictions = {
		+	r1 = {
		+	table = ca_objects,
		+	type = ,
		+	settings = {
		+	minAttributesPerRow = 0,
		+	maxAttributesPerRow = 255,
		+	minimumAttributeBundlesToDisplay = 1
		+	}
		+	}
		+	}
		+	},
		+	</pre></code>
		+
		+	The element set opens with its “code name” (in this example it is “description”). As with lists and locales, the code name opens this set and will be referred to later in the profile. Important: make sure that each element set you defined has a unique code name within the profile. If you create two element sets with the same code name, only the last defined element set will be available.
		+
		+	====DataTypes (AttributeTypes)====
		+	Each element in an element set must be declared with a specific datatype (sometimes referred to as attribute types). These configure what kind of data will be entered into a specific element, how it will be formatted, and how it will be stored. At this time there are 20 [[AttributeTypes]] to chose from.
		+
		+	Lists are unique because they require reference code names defined in your list definitions. For example:
		+
		+	<code><pre>
		+	pbcoreFormatPhysical_video = {
		+	datatype = List,
		+	preferred_labels = {
		+	en_US = {
		+	name = Format Physical: Video,
		+	description = "Use the descriptor formatPhysical to identify the format of a particular version or rendition of a media item."
		+	}
		+	},
		+	list = pbcore_format_physical_types_video,
		+	</pre></code>
		+
		+	In this element set the code name is pbcoreFormatPhysical_video, its datatype is List, the preferred labels are in English and are Format Physical: Video. A description has been added and will appear as help text in the cataloging interface when the label is moused over. The list is defined from a code name defined in the list definitions. In this particular case its pbcore_format_physical_types_video. This links the element set with its corresponding List in list definitions creating the necessary code for the drop-down menu style controlled vocabulary. See [[Creating Lists]] for more details.
		+
		+	====Settings====
		+	Next, the settings define how and what the data field will display. Settings vary based upon the datatype of the element. For a text element settings include width, height, maximum and minimum characters allowed. Refer to [[AttributeTypes]] for specific settings.
		+
		+	If you would like to make a particular text field a required data entry point, set your minimum characters to 1. This will require at least 1 character to be entered in the field before the element set can be saved.
		+
		+	====Type Restrictions====
		+	Type restrictions do pretty much what they sound like they do – they restrict element sets according to types. More precisely they restrict element sets to specific item types (objects, entities, places, occurrences, etc.) and define how attributes can be created and displayed. It is possible to target a restriction to an item type in general or to a specific type value for an item. For example, if you have defined an object type (in the object_types system list) of “periodical”, you can restrict an element set to be valid for only objects that are periodicals. Attributes of that element set will appear on editing forms only for periodicals (and whatever else it is bound to via type restrictions). Type restrictions can be assigned to as many item types as necessary for that particular element set.
		+
		+	Defining a restriction by, for example, object types creates unique cataloging interfaces based on the kinds of objects that you have in your collection. For instance, you may want to have different data entry fields for multimedia content than you want for paper-based materials. By defining these object types in the list definitions and then linking them to “type” under type restrictions, you can create object type-specific cataloging interfaces.
		+
		+	<code><pre>
		+	type_restrictions = {
		+	r1 = {
		+	table = ca_objects,
		+	type = moving_images,
		+	settings = {
		+	minAttributesPerRow = 0,
		+	maxAttributesPerRow = 255,
		+	minimumAttributeBundlesToDisplay = 1
		+	}
		+	}
		+	</pre></code>
		+
		+	Note that the item type specification – what type of item the restriction is bound to – is called “table” in the profile code. This is because the item types are specified using the names for their tables in the CollectiveAccess database. Specific table names are used for these [[Primary Types]].
		+
		+	Each type restriction can take settings. Currently defined settings values are:
		+
		+	{\|border="1" cellspacing="0" cellpadding="5"
		+	\|\|'''Setting'''\|\|'''Value'''
		+	\|-
		+	\|\|minAttributesPerRow\|\|Minimum number of attributes of this kind that must be associated with an item; set to zero to make the attribute optional; valid value must be a positive integer.
		+	\|-
		+	\|\|maxAttributesPerRow\|\|Maximum number of attributes of this kind that can be associated with an item; set to zero or do not set to enforce no limit; valid value must be a positive integer.
		+	\|-
		+	\|\|minimumAttributeBundlesToDisplay\|\|The minimum number of attribute bundles to show in an editing form. If the number of actual attributes is less than this number then the user interface will show empty form bundles to reach this number. This number should be less than or equal to the maximum number of attributes per row; valid values are positive integers.
		+	\|-
		+	\|}
		+
		+	===User Interface Definitions===
		+	User interface definitions configure the layout of element sets within the cataloging system. Here you can bring together all the element sets and arrange them into a manageable cataloging interface through designation of [[Screens]] and [[Bundles]].
		+
		+	Screens are used to group metadata attributes and create a desired cataloging workflow. Bundles are user interface elements that can be placed on each screen. They can be editable attributes of a specific element set or editable database fields intrinsic to a specific item type. Or they can be user interfaces that allow cataloguers to establish relationships with other items, add and remove items from sets and manage an item’s location in a larger hierarchy. Bundles are so named because they are essentially black-boxes that encapsulate various functionality. You don’t need to know how they implement this functionality. You need only place them where you want them to be.
		+
		+	That user interfaces are just ordered arrangements of form elements and controls – bundles – makes them highly configurable. Perhaps you want only Title and ID on the first screen, additional data on the second screen, and multimedia on the third. In Figure 2 you can see the various tabs in the left side navigation in Providence. These tabs are actually defined as screens in the user interface definitions found in the installation profile.
		+
		+	'''INSERT FIGURE 2'''
		+
		+	To organize the data fields on each screen, bundles are listed out in a bundle list:
		+
		+	<code><pre>
		+	bundles = {
		+	preferred_labels = {
		+	bundle = preferred_labels,
		+	label = {
		+	en_US = Title
		+	},
		+	add_label = {
		+	en_US = Add title
		+	}
		+	},
		+	idno = { bundle = idno },
		+	source_id = { bundle = source_id },
		+	status = { bundle = status },
		+	access = { bundle = access },
		+	ca_attribute_description = { bundle = ca_attribute_description},
		+	ca_attribute_dc_type = { bundle = ca_attribute_dc_type},
		+	ca_attribute_dc_format = { bundle = ca_attribute_dc_format}
		+	}
		+	</pre></code>
		+
		+	Note that each entry in the bundle list is actually comprised of several parts: a unique code as key and an associative array as value. At a minimum, the value array must define a bundle using the ‘bundle’ key and a valid bundle name as the value. Depending upon the bundle being listed, other settings can be passed as well.
		+
		+	The list of valid bundles varies according to the type of item being edited. The object editor supports certain bundles that the entities editor does not. All editors support attribute bundles. To derive the bundle name for a specific element_set simply preface the element code with ‘ca_attribute_’ For example, the element_set creation_date would have a bundle name of ca_attribute_creation_date. The bundle names for various intrinsic database fields are the field names themselves. These [[Intrinsic Bundles]] names for other user interface elements are unique to the [[Primary Types]].

AttributeTypes

2010-09-07T20:40:35Z

Show changes

Common Metadata Elements

2010-09-06T21:27:20Z

← Older revision		Revision as of 21:27, 6 September 2010
(5 intermediate revisions not shown)
Line 1:		Line 1:
	This section covers Metadata Bundles you may encounter in your installation of CollectiveAccess. You may, of course, create any Metadata Element of your choice using the [[Configuring Metadata Elements\|Online Interface]]. Advanced users may want to consult the [[Generic Bundles]] documentation.		This section covers Metadata Bundles you may encounter in your installation of CollectiveAccess. You may, of course, create any Metadata Element of your choice using the [[Configuring Metadata Elements\|Online Interface]]. Advanced users may want to consult the [[Generic Bundles]] documentation.

-	;Access :	+	;Access : This drop-down menu controls who can view your record. You may create access levels for different [[User Groups]], or determine whether the record appears on your public website, if you have [[Pawtucket]] installed. Access bundles appear separately for media representations, allowing you to choose different access levels for a record and its attached media.
-	;Alternate Title :	+	;Alternate Title : This bundle allow you to specify an alternate title for your record to make it more easy to locate within the system. There are two types of Alternate Titles, which are identified by an accompanying drop-down menu. Selecting “Alternates” from the drop-down menu will allow you to identify this title as a second title for your media (for example, if a painting has titles in English and German). In this instance, both are correct titles and can be used to refer to your record within the system. Selecting “Use For” will allow the system to identify your media by this title, but it will never display it as an alternative. For example, if your painting, “Red No. 1,” is commonly referred to as “Red Number 1” or "Red #1," entering this as a “Use For” title will train the system to retrieve the correct record even when the misspelled name is entered.
-	;Caption :	+	;Caption : This Metadata Element commonly appears in the Media Representation Editor, allowing you to specify a caption for your media.
-	;Purchase Price :	+	;Purchase Price : This appears in some Object Lot editors to specify how much a collection object was purchased for. This and other money-related elements (appraisal values, resale values, etc) take the "currency" [[AttributeTypes\|data type]].
	;Dates : This metadata element typically uses the DateRange [[AttributeTypes\|datatype]], which accepts dates and date ranges in a variety of [[DateAndTimeFormats\|formats]]. Often this bundle will also contain a drop-down menu of qualifiers, allowing you to specify publication dates, creation dates, performance dates, etc. You can edit these qualifiers by managing [[Creating Lists\|Lists]] in your system. This is usually a repeatable field, allowing you to catalog multiple temporal events for your collection item.		;Dates : This metadata element typically uses the DateRange [[AttributeTypes\|datatype]], which accepts dates and date ranges in a variety of [[DateAndTimeFormats\|formats]]. Often this bundle will also contain a drop-down menu of qualifiers, allowing you to specify publication dates, creation dates, performance dates, etc. You can edit these qualifiers by managing [[Creating Lists\|Lists]] in your system. This is usually a repeatable field, allowing you to catalog multiple temporal events for your collection item.
-	;Description (internal use) :	+	;Description (internal use) : Description bundles allow you to catalog descriptive text about your collection items. You may specify internal-only information for your reference. Currently, there is no difference in the functionality of bundles marked "internal." Access levels for individual Metadata Elements are currently in development and will be included in the CollectiveAccess 1.0 release. To omit "internal" metadata elements from your public website, if you have one, simply [[Customizing Pawtucket - Section by section\|configure]] your system not to display them.
-	;Description (public) :	+	;Description (public) : Description bundles allow you to catalog descriptive text about your collection items. You may specify that this is public information for your reference. Currently, there is no difference in the functionality of bundles marked "public" or "internal." Access levels for individual Metadata Elements are currently in development and will be included in the CollectiveAccess 1.0 release. To public "public" metadata elements to your public website, if you have one, simply [[Customizing Pawtucket - Section by section\|configure]] your system to display them.
	;Dimensions : The dimensions bundle often contains individual fields for length, width and height that accept the "Length" [[AttributeTypes\|datatype]]. These fields accept measurements in a variety of [[Measurement Input Formats\|units]].		;Dimensions : The dimensions bundle often contains individual fields for length, width and height that accept the "Length" [[AttributeTypes\|datatype]]. These fields accept measurements in a variety of [[Measurement Input Formats\|units]].
	;Display Labels (non-preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].		;Display Labels (non-preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].
	;Display Labels (preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].		;Display Labels (preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].
	;[[Georeferencing\|Georeference]] :		;[[Georeferencing\|Georeference]] :
-	;Extent :	+	;Extent :
	;[[Using the AAT\|Getty Art & Architecture Thesaurus (AAT)]] :		;[[Using the AAT\|Getty Art & Architecture Thesaurus (AAT)]] :
-	~~;Hierarchy Location :~~
	;Idno : An Identification Number, whether assigned by the user or automatically generated by the system. You can read more about Id Numbers [[ID Numbers\|here]]		;Idno : An Identification Number, whether assigned by the user or automatically generated by the system. You can read more about Id Numbers [[ID Numbers\|here]]
	;[[Using the LCSH\|Library of Congress Subject Headings]] :		;[[Using the LCSH\|Library of Congress Subject Headings]] :
	;[[Media Representation Bundle\|Media Representation]] :		;[[Media Representation Bundle\|Media Representation]] :
-	;Type :	+	;Type (aka subtype) : While [[Primary Types]] are permanently configured for your system, you may assign more specific Types to better classify your collection items. For example, the Objects Primary Type may be sub-categorized into Paintings, Sculpture, Photographs, etc. Entities commonly divided into sub-types named Individuals and Organizations. These Types determine what Editor and [[Configuring Metadata Elements\|Metadata Elements]] are used to create and view your record, and therefore cannot be changed once the record is created.
	;[[Location in Hierarchy Bundle\|Location in Hierarchy]] :		;[[Location in Hierarchy Bundle\|Location in Hierarchy]] :
	;Relationship Bundle : This look-up field creates a [[Relationships\|relationship]] between the current record and another record of a specified [[Primary Types\|Type]]. The record you wish to relate must already exist before attempting to create a relationship. To select the second record, type at least the first three characters of its Name or Title into the look-up field. A list of available records will appear for you to choose from. When the record is selected, you may define the relationship by selecting a Relationship Qualifier from the following drop-down list. This field is repeatable, and you can create as many relationships for a record as you wish. For more information, see [[Relationships]].		;Relationship Bundle : This look-up field creates a [[Relationships\|relationship]] between the current record and another record of a specified [[Primary Types\|Type]]. The record you wish to relate must already exist before attempting to create a relationship. To select the second record, type at least the first three characters of its Name or Title into the look-up field. A list of available records will appear for you to choose from. When the record is selected, you may define the relationship by selecting a Relationship Qualifier from the following drop-down list. This field is repeatable, and you can create as many relationships for a record as you wish. For more information, see [[Relationships]].

Cataloging in CollectiveAccess Manual

2010-09-04T15:14:37Z

Adding hyperlink to version 2

← Older revision		Revision as of 15:14, 4 September 2010
Line 1:		Line 1:
-	[[File:Cataloging_generic_-v.1-.pdf‎]]	+	* [[File:Cataloging_generic_-v.1-.pdf‎]]
		+	* [http://www.collectiveaccess.org/docs/Cataloging_generic_v2.pdf File:Cataloging_generic_v2.pdf]

	[[Category:Finish writing now]]		[[Category:Finish writing now]]

User:AshLin

2010-09-04T15:12:17Z

New user account

New page

Geocode Attribute Type Notes

2010-09-03T02:34:59Z

← Older revision		Revision as of 02:34, 3 September 2010
Line 9:		Line 9:
	=== Google Maps integration ===		=== Google Maps integration ===

-	The Google Maps mapping service is used to produce maps displaying your coordinates. The Geocode attribute ~~supports both~~ version 2 ~~and~~ 3 of the Google Maps API~~. You can choose which version to use in your CA installation by setting~~ the ''google_api'' directive in ~~your~~ [[globalConfigurationFile\|global.conf]] file. ~~The two version have their respective advantages (which is why we support both).~~	+	The Google Maps mapping service is used to produce maps displaying your coordinates. The Geocode attribute used to support either version 2 or 3 of the Google Maps API, selectable via the ''google_api'' directive in the [[globalConfigurationFile\|global.conf]] file. As of August 2010, only the v3 API is supported since v2 is now officially deprecated by Google. Any old v2 configuration in your installation (assuming you installed prior to August 2010) will be ignored.
-		+
-	~~{\| border="1" cellspacing="0" cellpadding="5"~~	+
-	~~\|\|'''Version'''\|\|'''Pros'''\|\|'''Cons'''~~	+
-	\|-	+
-	~~\|\|2\|\|Supports drawing~~ of ~~polygons; CA uses this feature to draw a shaded polygon representing~~ the ~~area delineated~~ by ~~multiple coordinates\|\|Bigger and slower than version 3; requires a [http://code~~.~~google.com/apis/maps/signup.html free API key] from Google~~	+
-	\|-	+
-	~~\|\|3\|\|Does not require an API key; smaller and faster loading than version 2\|\|Does not support polylines; CA renders areas as a set of markers which doesn't look as nice as a shaded polygon~~	+
-	\|}	+
-		+
-	~~You can switch between API versions at any time by changing the setting~~ in your ~~''global.conf'' file. If~~ you ~~decide~~ to ~~use version 2~~ be ~~sure to sign up for your API key~~.	+

Frequently Asked Questions

2010-09-03T02:32:05Z

← Older revision		Revision as of 02:32, 3 September 2010
Line 38:		Line 38:
	# ''Can CollectiveAccess watermark images?'' <br/> CA can add [[Image_Watermarking\|visible watermarks]] to derivative images. Invisible watermarks, like those created by [http://www.digimarc.com DigiMarc] are not currently supported, but we are considering support for it in the future.<br/><br/>		# ''Can CollectiveAccess watermark images?'' <br/> CA can add [[Image_Watermarking\|visible watermarks]] to derivative images. Invisible watermarks, like those created by [http://www.digimarc.com DigiMarc] are not currently supported, but we are considering support for it in the future.<br/><br/>
	# ''Does CollectiveAccess extract metadata embedded in uploaded media?'' <br/> Yes. IPTC, XMP and EXIF metadata are extracted from uploaded images and stored in the database. We are working on a system for mapping embedded metadata from uploads into specific fields in your schema, which will make extraction much more useful. <br/><br/>		# ''Does CollectiveAccess extract metadata embedded in uploaded media?'' <br/> Yes. IPTC, XMP and EXIF metadata are extracted from uploaded images and stored in the database. We are working on a system for mapping embedded metadata from uploads into specific fields in your schema, which will make extraction much more useful. <br/><br/>
-	# ''Can CollectiveAccess embed metadata into media provided for download?'' <br/> Not yet. We're planning to support this in the ~~first half~~ of 2010. <br/><br/>	+	# ''Can CollectiveAccess embed metadata into media provided for download?'' <br/> Not yet. We're planning to support this before the end of 2010. <br/><br/>
	# ''Can I ingest media into CollectiveAccess in batches?'' <br/> Yes. You will have to write a script to do so that takes into account the specific needs of your ingestion process, including the specifics of how media should be mapped to existing data. Send a message to support@collectiveaccess.org if you want example code to work from.<br/><br/>		# ''Can I ingest media into CollectiveAccess in batches?'' <br/> Yes. You will have to write a script to do so that takes into account the specific needs of your ingestion process, including the specifics of how media should be mapped to existing data. Send a message to support@collectiveaccess.org if you want example code to work from.<br/><br/>
	# ''Can CollectiveAccess search text contained within PDF and/or Microsoft Word files?'' <br/> Yes, so long as you have the appropriate helper applications installed on your server: [http://www.abisource.com/ ABIWord] (for extraction of text from Microsoft Word files) and/or [http://www.foolabs.com/xpdf/download.html PDFToText] (for extraction of text from PDF files). You'll also need to make sure you've configured you [[External_Application_Configuration\|external_applications.conf]] file with the proper paths to each helper application.<br/><br/>		# ''Can CollectiveAccess search text contained within PDF and/or Microsoft Word files?'' <br/> Yes, so long as you have the appropriate helper applications installed on your server: [http://www.abisource.com/ ABIWord] (for extraction of text from Microsoft Word files) and/or [http://www.foolabs.com/xpdf/download.html PDFToText] (for extraction of text from PDF files). You'll also need to make sure you've configured you [[External_Application_Configuration\|external_applications.conf]] file with the proper paths to each helper application.<br/><br/>

File:Ui.png

2010-09-03T02:25:51Z

Adding image note: This is the media image!

← Older revision	Revision as of 02:25, 3 September 2010
Line 1:	Line 1:

	+	{{ImageNote\|id=1\|x=28\|y=221\|w=162\|h=118\|dimx=919\|dimy=720\|style=2}}
	+	This is the media image!
	+	{{ImageNoteEnd\|id=1}}

MediaWiki:LAPI.js

2010-09-03T02:25:15Z

MediaWiki:ImageAnnotatorEditSummaries

2010-09-03T02:21:35Z

Created page with '{{#if: {{{live|}}}||*MediaWiki:ImageAnnotatorAddSummary (wikitext; must be enclosed by <nowiki>; $1 is replaced): }}{{#ifexist: MediaWiki:ImageAnnotatorAddSummary|<span cl…'

MediaWiki:ImageAnnotatorUITexts

2010-09-03T02:21:03Z

Created page with '{{#if: {{{live|}}}||*/{{{lang}}}}} (simple text only, no markup): }}<span class="wpImageAnnotatorCancel">{{#ifexist…'

MediaWiki:ImageAnnotatorTexts

2010-09-03T02:20:28Z

Created page with '{{#if: {{{live|}}}|<includeonly><div id="wpImageAnnotatorWrapper" style="display:none;"></includeonly>}} __NOTOC__ {{#if: {{{lang|}}} |<div class="wpImageAnnotatorTexts" lang="{…'

Template:ImageNoteColors

2010-09-03T02:19:50Z

protected "[[Template:ImageNoteColors]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:ImageNoteControl

2010-09-03T02:19:10Z

protected "[[Template:ImageNoteControl]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:InlineImageAnnotations

2010-09-03T02:18:25Z

protected "[[Template:InlineImageAnnotations]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:ImageAnnotations

2010-09-03T02:17:35Z

protected "[[Template:ImageAnnotations]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:ImageWithNotes

2010-09-03T02:16:11Z

protected "[[Template:ImageWithNotes]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:ImageNoteEnd

2010-09-03T02:15:29Z

protected "[[Template:ImageNoteEnd]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

Template:ImageNote

2010-09-03T02:14:54Z

protected "[[Template:ImageNote]]" [edit=sysop] (indefinite) [move=sysop] (indefinite)

New page

MediaWiki:Common.js

2010-09-03T02:13:54Z

Created page with '- Any JavaScript here will be loaded for all users on every page load.: if (wgNamespaceNumber != -1) importScript ('MediaWiki:Gadget-ImageAnnotator.js');'

MediaWiki:Gadget-ImageAnnotator

2010-09-03T02:13:19Z

Created page with 'Image annotator extension for MediaWiki. Does what it sounds like it does.'

MediaWiki:Gadgets-definition

2010-09-03T02:12:40Z

MediaWiki:LAPI.js

2010-09-03T02:09:01Z

MediaWiki:Gadget-DisableImageAnnotator.js

2010-09-03T02:07:59Z

Created page with '// <source lang="javascript"> - Small gadget to disable MediaWiki:Gadget-ImageAnnotator.js, which is enabled by default for everyone here at the Commons.: var ImageA…'

MediaWiki:AjaxSubmit.js

2010-09-03T02:06:47Z

Created page with '// ajaxSubmit // Submit a form through Ajax. Doesn't handle file uploads yet. // // Parameters: // form DOM element The form to submit // button opti…'

MediaWiki:UIElements.js

2010-09-03T02:06:15Z

Created page with '// <source lang="javascript"> /* Read UI elements from the DOM. Used by the upload form rewrite. Author: User:Lupo, March 2008 License: Quadruple licensed GFDL, GPL, …'

MediaWiki:Tooltips.js

2010-09-03T02:05:32Z

Created page with '// <source lang="javascript"> /* Cross-browser tooltip support for MediaWiki. Author: User:Lupo, March 2008 License: Quadruple licensed GFDL, GPL, LGPL and Creative…'

MediaWiki:TextCleaner.js

2010-09-03T02:05:01Z

Created page with '// <source lang="javascript"> /* Wikitext sanitation for MediaWiki Author: User:Lupo, January 2008 License: Quadruple licensed GFDL, GPL, LGPL and Creative Commons At…'

MediaWiki:LAPI.js

2010-09-03T02:04:35Z

Created page with '// <source lang=javascript"> /* Small JS library containing stuff I use often. Author: User:Lupo, June 2009 License: Quadruple licensed GFDL, GPL, LGPL and Creative…'

MediaWiki:ImageAnnotatorConfig.js

2010-09-03T02:04:03Z

Created page with '// <source lang="javascript"> /* Site-wide configurations and start of the ImageAnnotator gagdet. Split into a separate file for three reasons: 1. It separates the config…'

MediaWiki:Gadget-ImageAnnotator.js

2010-09-03T02:03:22Z

Created page with '// <source lang="javascript"> /* THIS IS ImageAnnotator VERSION 2.2 Image annotations. Draw rectangles onto image thumbnail displayed on image description page and associ…'

Preferences

2010-09-02T21:09:26Z

New page

To edit system preferences navigate to Manage > My Preferences in the Global Navigation menu.

Your preferences are divided into five different screens: User Interface, Cataloguing, Media, Units of Measurement, and User Profile.

=== User Interface ===
;User Interface Locale : This setting determines the language used in menus, informational text and the User Interface. This setting <i>will not</i> affect the other languages you have configured for cataloging purposes.
;User Interface Theme: Currently there is only one theme included in the standard CollectiveAccess installation. However, should you choose to design your own theme, you can select it here.
;Show current location as "breadcrumb" trail: This control turns the [[User Interface|Breadcrumb Trail]] display on or off.

=== Cataloguing ===
;Default cataloguing locale: If you have multiple locales defined for your archive, you can choose the default language here
;Item label display mode: This setting allows you to choose a display mode if you are cataloging titles in multiple languages. You may choose to display labels in your primary language, in the item's language, or both.
;Object editor user interface: Selects which Editor to use when editing Objects.
;Object lot editor user interface: Selects which Editor to use when editing Object Lots.
;Entity editor user interface: Selects which Editor to use when editing Entities.
;Place editor user interface: Selects which Editor to use when editing Places.
;Occurrence editor user interface: Selects which Editor to use when editing Occurrences.
;Collection editor user interface: Selects which Editor to use when editing Collections.
;Storage location editor user interface: Selects which Editor to use when editing Storage Locations.
;Object representation editor user interface: Selects which Editor to use when editing Object Representations.
;Representation annotation editor user interface: Selects which Editor to use when editing Representation Annotations.
;Sets editor user interface: Selects which Editor to use when editing Sets.
;Set item editor user interface: Selects which Editor to use when editing Set Items.
;List editor user interface: Selects which Editor to use when editing Lists.
;List item editor user interface: Selects which Editor to use when editing List Items.

=== Media ===

User Interface

2010-09-02T20:13:03Z

← Older revision		Revision as of 20:13, 2 September 2010
Line 17:		Line 17:
	;Results Controls : These controls allow you to navigate through your search results after conducting a [[Basic Search\|Search]] or [[Browse]]. Use the arrows to view your search results one by one. Clicking RESULTS will take you back to your full list of search results.		;Results Controls : These controls allow you to navigate through your search results after conducting a [[Basic Search\|Search]] or [[Browse]]. Use the arrows to view your search results one by one. Clicking RESULTS will take you back to your full list of search results.

-	;Inspector : This displays the record [[Primary Types\|Type]], ID Number, Title and images pertaining to your record. You can use the arrows to scroll through the available media, and click the thumbnail image to open the [[~~media viewer~~]]. A [[Color Coding the Inspector\|customizable]] icon and colored border help to differentiate between different Editor Types.	+	;Inspector : This displays the record [[Primary Types\|Type]], ID Number, Title and images pertaining to your record. You can use the arrows to scroll through the available media, and click the thumbnail image to open the [[Media Viewer]]. A [[Color Coding the Inspector\|customizable]] icon and colored border help to differentiate between different Editor Types.

	;Local Navigation : This menu allows the user to navigate between the different Screens of an Editor. When searching for records, this sidebar contains shortcuts for printing and exporting your results.		;Local Navigation : This menu allows the user to navigate between the different Screens of an Editor. When searching for records, this sidebar contains shortcuts for printing and exporting your results.
Line 23:		Line 23:
	;Drop-down Menus : These menus are derived from [[Creating Lists\|customizable lists]], allowing the user to create a controlled authority for select [[Common Metadata Elements\|metadata elements]].		;Drop-down Menus : These menus are derived from [[Creating Lists\|customizable lists]], allowing the user to create a controlled authority for select [[Common Metadata Elements\|metadata elements]].

-	;Fields : These forms allow the user to enter information freely. Fields can be [[~~Customizing~~ Metadata Elements\|customized]] to accept only certain [[AttributeTypes\|data types]] such as text, numerical values, currencies and date ranges.	+	;Fields : These forms allow the user to enter information freely. Fields can be [[Configuring Metadata Elements\|customized]] to accept only certain [[AttributeTypes\|data types]] such as text, numerical values, currencies and date ranges.

	;"Add" Buttons : These buttons appear below repeating fields, enabling you to add as many instances of those fields as is allowed by your [[Configuring Metadata Elements\|system configuration]].		;"Add" Buttons : These buttons appear below repeating fields, enabling you to add as many instances of those fields as is allowed by your [[Configuring Metadata Elements\|system configuration]].

← Older revision		Revision as of 21:27, 6 September 2010
(5 intermediate revisions not shown)
Line 1:		Line 1:
	This section covers Metadata Bundles you may encounter in your installation of CollectiveAccess. You may, of course, create any Metadata Element of your choice using the [[Configuring Metadata Elements\|Online Interface]]. Advanced users may want to consult the [[Generic Bundles]] documentation.		This section covers Metadata Bundles you may encounter in your installation of CollectiveAccess. You may, of course, create any Metadata Element of your choice using the [[Configuring Metadata Elements\|Online Interface]]. Advanced users may want to consult the [[Generic Bundles]] documentation.

-	;Access :	+	;Access : This drop-down menu controls who can view your record. You may create access levels for different [[User Groups]], or determine whether the record appears on your public website, if you have [[Pawtucket]] installed. Access bundles appear separately for media representations, allowing you to choose different access levels for a record and its attached media.
-	;Alternate Title :	+	;Alternate Title : This bundle allow you to specify an alternate title for your record to make it more easy to locate within the system. There are two types of Alternate Titles, which are identified by an accompanying drop-down menu. Selecting “Alternates” from the drop-down menu will allow you to identify this title as a second title for your media (for example, if a painting has titles in English and German). In this instance, both are correct titles and can be used to refer to your record within the system. Selecting “Use For” will allow the system to identify your media by this title, but it will never display it as an alternative. For example, if your painting, “Red No. 1,” is commonly referred to as “Red Number 1” or "Red #1," entering this as a “Use For” title will train the system to retrieve the correct record even when the misspelled name is entered.
-	;Caption :	+	;Caption : This Metadata Element commonly appears in the Media Representation Editor, allowing you to specify a caption for your media.
-	;Purchase Price :	+	;Purchase Price : This appears in some Object Lot editors to specify how much a collection object was purchased for. This and other money-related elements (appraisal values, resale values, etc) take the "currency" [[AttributeTypes\|data type]].
	;Dates : This metadata element typically uses the DateRange [[AttributeTypes\|datatype]], which accepts dates and date ranges in a variety of [[DateAndTimeFormats\|formats]]. Often this bundle will also contain a drop-down menu of qualifiers, allowing you to specify publication dates, creation dates, performance dates, etc. You can edit these qualifiers by managing [[Creating Lists\|Lists]] in your system. This is usually a repeatable field, allowing you to catalog multiple temporal events for your collection item.		;Dates : This metadata element typically uses the DateRange [[AttributeTypes\|datatype]], which accepts dates and date ranges in a variety of [[DateAndTimeFormats\|formats]]. Often this bundle will also contain a drop-down menu of qualifiers, allowing you to specify publication dates, creation dates, performance dates, etc. You can edit these qualifiers by managing [[Creating Lists\|Lists]] in your system. This is usually a repeatable field, allowing you to catalog multiple temporal events for your collection item.
-	;Description (internal use) :	+	;Description (internal use) : Description bundles allow you to catalog descriptive text about your collection items. You may specify internal-only information for your reference. Currently, there is no difference in the functionality of bundles marked "internal." Access levels for individual Metadata Elements are currently in development and will be included in the CollectiveAccess 1.0 release. To omit "internal" metadata elements from your public website, if you have one, simply [[Customizing Pawtucket - Section by section\|configure]] your system not to display them.
-	;Description (public) :	+	;Description (public) : Description bundles allow you to catalog descriptive text about your collection items. You may specify that this is public information for your reference. Currently, there is no difference in the functionality of bundles marked "public" or "internal." Access levels for individual Metadata Elements are currently in development and will be included in the CollectiveAccess 1.0 release. To public "public" metadata elements to your public website, if you have one, simply [[Customizing Pawtucket - Section by section\|configure]] your system to display them.
	;Dimensions : The dimensions bundle often contains individual fields for length, width and height that accept the "Length" [[AttributeTypes\|datatype]]. These fields accept measurements in a variety of [[Measurement Input Formats\|units]].		;Dimensions : The dimensions bundle often contains individual fields for length, width and height that accept the "Length" [[AttributeTypes\|datatype]]. These fields accept measurements in a variety of [[Measurement Input Formats\|units]].
	;Display Labels (non-preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].		;Display Labels (non-preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].
	;Display Labels (preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].		;Display Labels (preferred) : For advanced users, more information about Label Bundles is available [[Label Bundles\|here]].
	;[[Georeferencing\|Georeference]] :		;[[Georeferencing\|Georeference]] :
-	;Extent :	+	;Extent :
	;[[Using the AAT\|Getty Art & Architecture Thesaurus (AAT)]] :		;[[Using the AAT\|Getty Art & Architecture Thesaurus (AAT)]] :
-	~~;Hierarchy Location :~~
	;Idno : An Identification Number, whether assigned by the user or automatically generated by the system. You can read more about Id Numbers [[ID Numbers\|here]]		;Idno : An Identification Number, whether assigned by the user or automatically generated by the system. You can read more about Id Numbers [[ID Numbers\|here]]
	;[[Using the LCSH\|Library of Congress Subject Headings]] :		;[[Using the LCSH\|Library of Congress Subject Headings]] :
	;[[Media Representation Bundle\|Media Representation]] :		;[[Media Representation Bundle\|Media Representation]] :
-	;Type :	+	;Type (aka subtype) : While [[Primary Types]] are permanently configured for your system, you may assign more specific Types to better classify your collection items. For example, the Objects Primary Type may be sub-categorized into Paintings, Sculpture, Photographs, etc. Entities commonly divided into sub-types named Individuals and Organizations. These Types determine what Editor and [[Configuring Metadata Elements\|Metadata Elements]] are used to create and view your record, and therefore cannot be changed once the record is created.
	;[[Location in Hierarchy Bundle\|Location in Hierarchy]] :		;[[Location in Hierarchy Bundle\|Location in Hierarchy]] :
	;Relationship Bundle : This look-up field creates a [[Relationships\|relationship]] between the current record and another record of a specified [[Primary Types\|Type]]. The record you wish to relate must already exist before attempting to create a relationship. To select the second record, type at least the first three characters of its Name or Title into the look-up field. A list of available records will appear for you to choose from. When the record is selected, you may define the relationship by selecting a Relationship Qualifier from the following drop-down list. This field is repeatable, and you can create as many relationships for a record as you wish. For more information, see [[Relationships]].		;Relationship Bundle : This look-up field creates a [[Relationships\|relationship]] between the current record and another record of a specified [[Primary Types\|Type]]. The record you wish to relate must already exist before attempting to create a relationship. To select the second record, type at least the first three characters of its Name or Title into the look-up field. A list of available records will appear for you to choose from. When the record is selected, you may define the relationship by selecting a Relationship Qualifier from the following drop-down list. This field is repeatable, and you can create as many relationships for a record as you wish. For more information, see [[Relationships]].

← Older revision		Revision as of 20:13, 2 September 2010
Line 17:		Line 17:
	;Results Controls : These controls allow you to navigate through your search results after conducting a [[Basic Search\|Search]] or [[Browse]]. Use the arrows to view your search results one by one. Clicking RESULTS will take you back to your full list of search results.		;Results Controls : These controls allow you to navigate through your search results after conducting a [[Basic Search\|Search]] or [[Browse]]. Use the arrows to view your search results one by one. Clicking RESULTS will take you back to your full list of search results.

-	;Inspector : This displays the record [[Primary Types\|Type]], ID Number, Title and images pertaining to your record. You can use the arrows to scroll through the available media, and click the thumbnail image to open the [[~~media viewer~~]]. A [[Color Coding the Inspector\|customizable]] icon and colored border help to differentiate between different Editor Types.	+	;Inspector : This displays the record [[Primary Types\|Type]], ID Number, Title and images pertaining to your record. You can use the arrows to scroll through the available media, and click the thumbnail image to open the [[Media Viewer]]. A [[Color Coding the Inspector\|customizable]] icon and colored border help to differentiate between different Editor Types.

	;Local Navigation : This menu allows the user to navigate between the different Screens of an Editor. When searching for records, this sidebar contains shortcuts for printing and exporting your results.		;Local Navigation : This menu allows the user to navigate between the different Screens of an Editor. When searching for records, this sidebar contains shortcuts for printing and exporting your results.
Line 23:		Line 23:
	;Drop-down Menus : These menus are derived from [[Creating Lists\|customizable lists]], allowing the user to create a controlled authority for select [[Common Metadata Elements\|metadata elements]].		;Drop-down Menus : These menus are derived from [[Creating Lists\|customizable lists]], allowing the user to create a controlled authority for select [[Common Metadata Elements\|metadata elements]].

-	;Fields : These forms allow the user to enter information freely. Fields can be [[~~Customizing~~ Metadata Elements\|customized]] to accept only certain [[AttributeTypes\|data types]] such as text, numerical values, currencies and date ranges.	+	;Fields : These forms allow the user to enter information freely. Fields can be [[Configuring Metadata Elements\|customized]] to accept only certain [[AttributeTypes\|data types]] such as text, numerical values, currencies and date ranges.

	;"Add" Buttons : These buttons appear below repeating fields, enabling you to add as many instances of those fields as is allowed by your [[Configuring Metadata Elements\|system configuration]].		;"Add" Buttons : These buttons appear below repeating fields, enabling you to add as many instances of those fields as is allowed by your [[Configuring Metadata Elements\|system configuration]].

← Older revision		Revision as of 22:18, 7 September 2010
Line 1:		Line 1:
	To work effectively with the software it is critical that you understand the fundamental components of a CollectiveAccess database. While CollectiveAccess provides great flexibility in terms of the specifics of your data model – you define your own fields, relationships and constraints – the general structure is fixed. CollectiveAccess defines fourteen types of records that model the world that your collection exists in. These are referred to as <b>Primary Types</b>:		To work effectively with the software it is critical that you understand the fundamental components of a CollectiveAccess database. While CollectiveAccess provides great flexibility in terms of the specifics of your data model – you define your own fields, relationships and constraints – the general structure is fixed. CollectiveAccess defines fourteen types of records that model the world that your collection exists in. These are referred to as <b>Primary Types</b>:

-	;Objects : Assets within a collection. Typically these are the physical or born-digital items you are managing.	+	;Objects (ca_objects) : Assets within a collection. Typically these are the physical or born-digital items you are managing.

-	;Entities : People or organizations. These are the creators, artists, donors, publishers and others involved in some way with your collection. Once an Entity is created in CollectiveAccess, it can be linked to other records within the database.	+	;Entities (ca_entities) : People or organizations. These are the creators, artists, donors, publishers and others involved in some way with your collection. Once an Entity is created in CollectiveAccess, it can be linked to other records within the database.

-	;Places : Physical locations, geographic or otherwise. Places are inherently hierarchical allowing you to nest more specific Place records within broader ones. As with Entities, once a Place is created it can be referred to throughout the system.	+	;Places (ca_places) : Physical locations, geographic or otherwise. Places are inherently hierarchical allowing you to nest more specific Place records within broader ones. As with Entities, once a Place is created it can be referred to throughout the system.

-	;Occurrences : Events or “things.” An Occurrence is a catch-all term used by CollectiveAccess to refer to contextual items that may require complex cataloguing but are not Entities, Places, Collections or Storage Locations. You can use Occurrences to support structured authorities for virtually any kind of item. Typically, Occurrences are used to support entries for historical events, exhibitions, film productions and bibliographies.	+	;Occurrences (ca_occurrences) : Events or “things.” An Occurrence is a catch-all term used by CollectiveAccess to refer to contextual items that may require complex cataloguing but are not Entities, Places, Collections or Storage Locations. You can use Occurrences to support structured authorities for virtually any kind of item. Typically, Occurrences are used to support entries for historical events, exhibitions, film productions and bibliographies.

-	;Collections : A defined group of objects. Collections can represent physical collections, symbolic collections of items associated by some criteria, or any other arbitrary grouping. Collections can handle complex cataloging, and therefore can be used for everything from simple grouping of objects to containers for collection-level finding aids. Collections should be used for long-term associations of objects in your institution. For temporary or administrative groupings of objects, see Sets.	+	;Collections (ca_collections) : A defined group of objects. Collections can represent physical collections, symbolic collections of items associated by some criteria, or any other arbitrary grouping. Collections can handle complex cataloging, and therefore can be used for everything from simple grouping of objects to containers for collection-level finding aids. Collections should be used for long-term associations of objects in your institution. For temporary or administrative groupings of objects, see Sets.

-	;Lots : Lots usually record basic intake information (donor, date of receipt, etc.) for a donation or acquisition, prior to Object-level cataloguing.	+	;Lots (ca_object_lots) : Lots usually record basic intake information (donor, date of receipt, etc.) for a donation or acquisition, prior to Object-level cataloguing.

-	;Sets : An ordered grouping of Objects defined by users for a specific purpose. Unlike Collections, Sets are ad-hoc groups of records created by a user for a practical purpose (e.g., a working checklist for an upcoming exhibition, or a set of Entities for which biographical information is needed). They are typically temporary groupings and thus not meant for collection-level cataloguing.	+	;Sets (ca_sets) : An ordered grouping of Objects defined by users for a specific purpose. Unlike Collections, Sets are ad-hoc groups of records created by a user for a practical purpose (e.g., a working checklist for an upcoming exhibition, or a set of Entities for which biographical information is needed). They are typically temporary groupings and thus not meant for collection-level cataloguing.

-	;Set Items : A record assigned to a Set. Records in a Set can take additional cataloguing, allowing one to contextualize and annotate records within an assigned Set. This enables the construction of Sets where each record contains Set-specific captions and links. This makes Sets and Set Items a great tool for constructing slideshows and tours based on your collection records.	+	;Set Items (ca_set_items) : A record assigned to a Set. Records in a Set can take additional cataloguing, allowing one to contextualize and annotate records within an assigned Set. This enables the construction of Sets where each record contains Set-specific captions and links. This makes Sets and Set Items a great tool for constructing slideshows and tours based on your collection records.

-	;Representations : Media (images, video, audio, PDFs) that documents an Object. While Representations often consist of just the media itself, they can take additional cataloguing that is specific to that media. This allows the addition of captions, credits, access information, rights and reproduction restrictions or any other type of information on a Representation-specific basis, if needed.	+	;Representations (ca_object_representations) : Media (images, video, audio, PDFs) that documents an Object. While Representations often consist of just the media itself, they can take additional cataloguing that is specific to that media. This allows the addition of captions, credits, access information, rights and reproduction restrictions or any other type of information on a Representation-specific basis, if needed.

-	;Storage Locations : Physical locations where Objects are stored. Like Places, Storage Locations are hierarchical – you can nest Locations to allow notation at any level of specificity (building, room, cabinet, drawer). Each Storage Location can take arbitrarily complex cataloguing, including access restrictions, map coordinates and other information. Storage Locations can be linked to both Objects and Lots, either directly, or through Object Events or Lot Events.	+	;Storage Locations (ca_storage_locations) : Physical locations where Objects are stored. Like Places, Storage Locations are hierarchical – you can nest Locations to allow notation at any level of specificity (building, room, cabinet, drawer). Each Storage Location can take arbitrarily complex cataloguing, including access restrictions, map coordinates and other information. Storage Locations can be linked to both Objects and Lots, either directly, or through Object Events or Lot Events.

-	;Lists : A simple or hierarchical group of List Items. Lists are used throughout CollectiveAccess in the following contexts: (1) as drop-down lists constraining the values of a field; (2) as controlled vocabularies whose List Items can be associated with Objects, Entities, Places, etc.; and (3) as system lists whose List Item values customize CollectiveAccess for application-level uses. All Lists must be assigned a unique List name, which is used internally to identify your List.	+	;Lists (ca_lists) : A simple or hierarchical group of List Items. Lists are used throughout CollectiveAccess in the following contexts: (1) as drop-down lists constraining the values of a field; (2) as controlled vocabularies whose List Items can be associated with Objects, Entities, Places, etc.; and (3) as system lists whose List Item values customize CollectiveAccess for application-level uses. All Lists must be assigned a unique List name, which is used internally to identify your List.

-	;List Items : The entries that comprise a List. All List Items have an intrinsic value and an identifier, as well as one or more text labels used for display.	+	;List Items (ca_list_items) : The entries that comprise a List. All List Items have an intrinsic value and an identifier, as well as one or more text labels used for display.

-	;Object Events : An event in the life-cycle of an Object. Each Object Event includes a planned date as well and the actual date of occurrence. Different types of Object Events (e.g., conservation events, movement events, loan events) can be recorded by defining Object Event types and assigning appropriate metadata elements for each type.	+	;Object Events (ca_object_events) : An event in the life-cycle of an Object. Each Object Event includes a planned date as well and the actual date of occurrence. Different types of Object Events (e.g., conservation events, movement events, loan events) can be recorded by defining Object Event types and assigning appropriate metadata elements for each type.

-	;Lot Events : An event in the life-cycle of a Lot. Each Lot Event includes a planned date as well and the actual date of occurrence. Different types of Lot Events (e.g., acquisition events, deaccession events) can be recorded by defining Lot Event types and assigning appropriate metadata elements for each type.	+	;Lot Events (ca_object_lot_events) : An event in the life-cycle of a Lot. Each Lot Event includes a planned date as well and the actual date of occurrence. Different types of Lot Events (e.g., acquisition events, deaccession events) can be recorded by defining Lot Event types and assigning appropriate metadata elements for each type.