Difference between revisions of "Location tracking"

From CollectiveAccess Documentation
Jump to: navigation, search
(Configuring Use History in the user interface)
(Configuring Use History in the user interface)
Line 10: Line 10:
 
[[File:UseHistory.png|600px]]
 
[[File:UseHistory.png|600px]]
  
In the bundle seen above the cataloguer has configured different colors and [[Bundle_Display_Templates|metadata display templates]] to showcase Accession, Loan, and Storage Location activity and data.  Each block is automatically sorted by the date chosen through the bundle settings for that table.  For example the Artwork loan is sorted on the "Loan Period" as seen via the dates on the far right-hand side. When a new relationship is created to any of the three configured tables a new segment appears in the stream in the appropriate order based on date.  In addition to the tables shown in the example, Occurrences, Movements, and Deaccessions can also be configured.
+
In the bundle seen above the cataloguer has configured different colors and templates to showcase Accession, Loan, and Storage Location activity and data.  Each block is automatically sorted by the date chosen through the bundle settings for that table.  For example Artwork loans are sorted on the "Loan Period" as seen via the dates on the far right-hand side. When a new relationship is created to any of the three configured tables a new segment will appear in the stream in the appropriate order based on date.  In addition to the tables shown in the example, Occurrences, Movements, and Deaccessions can also be configured.
 +
 
 +
The contents of each block in the stream are entirely configurable using [[Bundle_Display_Templates|metadata display templates]].  With this powerful syntax any metadata from the related record, or from those records related to the related record, can be displayed in the Use History bundle.  An example of that relationship traversing can be seen above in the Artwork loan blocks.  There, the "Borrower" is displayed using the below syntax which pulls entities related to the related loan:
 +
 
 +
<code><pre>
 +
<l>^ca_loans.preferred_labels</l><br>
 +
<ifdef code="ca_loans.loan_period">Loan Period:</ifdef> ^ca_loans.loan_period<br>
 +
Borrower: <unit relativeTo="ca_loans">
 +
<unit relativeTo="ca_entities" delimiter=", " restrictToRelationshipTypes="borrower">^ca_entities.preferred_labels</unit></unit>
 +
</pre></code>
  
 
===Configuring Use History in the installation profile===
 
===Configuring Use History in the installation profile===

Revision as of 16:43, 15 May 2014

Overview

Location tracking, or object use history, is a new tool in CollectiveAccess 1.5 that allows cataloguers to easily manage the activity of a collection object.

For those wishing to track a wide array of relationships in a single "use history stream" there is a new intrinsic bundle with robust settings called ca_objects_history or Object Use History. To use the bundle, simply place it on a user interface screen and adjust the settings, or include it in your installation profile.

Configuring Use History in the user interface

The Object Use History bundle has a variety of settings that customize the layout and contents of the location stream. Let's take a look at an example:

UseHistory.png

In the bundle seen above the cataloguer has configured different colors and templates to showcase Accession, Loan, and Storage Location activity and data. Each block is automatically sorted by the date chosen through the bundle settings for that table. For example Artwork loans are sorted on the "Loan Period" as seen via the dates on the far right-hand side. When a new relationship is created to any of the three configured tables a new segment will appear in the stream in the appropriate order based on date. In addition to the tables shown in the example, Occurrences, Movements, and Deaccessions can also be configured.

The contents of each block in the stream are entirely configurable using metadata display templates. With this powerful syntax any metadata from the related record, or from those records related to the related record, can be displayed in the Use History bundle. An example of that relationship traversing can be seen above in the Artwork loan blocks. There, the "Borrower" is displayed using the below syntax which pulls entities related to the related loan:

<l>^ca_loans.preferred_labels</l><br>
<ifdef code="ca_loans.loan_period">Loan Period:</ifdef> ^ca_loans.loan_period<br>
Borrower: <unit relativeTo="ca_loans">
<unit relativeTo="ca_entities" delimiter=", " restrictToRelationshipTypes="borrower">^ca_entities.preferred_labels</unit></unit>

Configuring Use History in the installation profile

Namespaces

Variants
Actions
Navigation
Tools
User
Personal tools