Difference between revisions of "History Tracking"

From CollectiveAccess Documentation
Jump to: navigation, search
(Created page with "'''Updated for v1.76''' == '''History Tracking is Location Tracking 2.0.''' == We've expanded the Location tracking feature to handle more nuanced poli...")
 
(Overview)
Line 11: Line 11:
 
# '''Direct object-location references.''' provided a simple history of objects' storage locations over time.  
 
# '''Direct object-location references.''' provided a simple history of objects' storage locations over time.  
 
# '''Movement-based location tracking''' recorded detailed information about how one or more objects are transferred between locations, in addition to the location history. This option was intended for collections where documenting chain of custody, insurance and packing are critical.
 
# '''Movement-based location tracking''' recorded detailed information about how one or more objects are transferred between locations, in addition to the location history. This option was intended for collections where documenting chain of custody, insurance and packing are critical.
# '''Workflow-based location tracking''' was designed for institutions with a robust notion of location and expands upon either of the preceding two options. In contrast with other methods, which all record relationships between objects and locations (with or without movements), workflow-based location tracking takes into consideration several types of records to determine the current location of an object, for example storage locations, exhibitions, loans, etc.
+
# '''Workflow-based location tracking''' was designed for institutions with a robust notion of location and expanded upon either of the preceding two options. In contrast with other methods, which all record relationships between objects and locations (with or without movements), workflow-based location tracking took into consideration several types of records to determine the current location of an object, for example storage locations, exhibitions, loans, etc.
  
Over time it became apparent that other records types required a similar type of description capturing a chain of custody or connections over time. For example, many users need to track a chronological ownership history between objects and entities, which was not possible through our original location tracking model. In this use case it's not sufficient to simply know the ownership order. Rather, it's important to be able to search and browse not only on the "current" collection in which that object resides but also to retrieve all objects "currently" in collections that meet certain criteria. To support these expanded needs we redesigned Location Tracking, creating a more general History Tracking feature.
+
Over time it became apparent that other records types required a similar type of description that captured a chain of custody or connections over time. For example, many users need to catalog a chronological ownership history between objects and entities, which was not possible through our original location tracking model. In this use case it's not sufficient to simply know who owned the object when. Rather, it's important to be able to search and browse not only the "current" collection in which the object resides but also to retrieve all objects "currently" in collections meeting certain criteria. To support these expanded needs we redesigned Location Tracking, creating a more general History Tracking feature.
  
  

Revision as of 21:24, 18 March 2019

Updated for v1.76


History Tracking is Location Tracking 2.0.

We've expanded the Location tracking feature to handle more nuanced policies for managing chronological relationships between an expanded set of record types in the database model.

Overview

Prior to version 1.76 we supported three ways for collection managers to determine the current location and location history of objects.

  1. Direct object-location references. provided a simple history of objects' storage locations over time.
  2. Movement-based location tracking recorded detailed information about how one or more objects are transferred between locations, in addition to the location history. This option was intended for collections where documenting chain of custody, insurance and packing are critical.
  3. Workflow-based location tracking was designed for institutions with a robust notion of location and expanded upon either of the preceding two options. In contrast with other methods, which all record relationships between objects and locations (with or without movements), workflow-based location tracking took into consideration several types of records to determine the current location of an object, for example storage locations, exhibitions, loans, etc.

Over time it became apparent that other records types required a similar type of description that captured a chain of custody or connections over time. For example, many users need to catalog a chronological ownership history between objects and entities, which was not possible through our original location tracking model. In this use case it's not sufficient to simply know who owned the object when. Rather, it's important to be able to search and browse not only the "current" collection in which the object resides but also to retrieve all objects "currently" in collections meeting certain criteria. To support these expanded needs we redesigned Location Tracking, creating a more general History Tracking feature.



update_sphinx

Namespaces

Variants
Actions
Navigation
Tools
User
Personal tools