Hi guys, I've noticed that the computer current location in collection objects_common is not getting updated, All the items I have in that field are blank and they do have locations assigned to them. Has anyone seen this before or does anyone have any hints why this is not working in my fcart clone?

Two possibilities to check: 1. That each Cataloging (collection object) record has a related Movement record; and 2. That in each related Movement record, these two fields both contain values: Current Location and Location Date. Note that the latter is also required: any related Movement records without a Location Date won't be included in the calculation of the current location, as the date that the object was (last) at that location is unknown/ambiguous. Aron P.S. Although this shouldn't affect database queries, I seem to recall having run across instances in CollectionSpace's UI, where it was necessary to refresh (or leave and then visit once again) the Cataloging record, to be able to view the updated Computed Current Location value. On Thu, Sep 8, 2016 at 3:39 PM, toolhater <toolhater@yahoo.com> wrote: > Hi guys, I've noticed that the computer current location in collection > objects_common is not getting updated, All the items I have in that field > are blank and they do have locations assigned to them. Has anyone seen this > before or does anyone have any hints why this is not working in my fcart > clone? > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > >

On Thursday, September 8, 2016 5:02 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote:

Sorry I've been out but I'm looking at your instructions to check the common_movements table. There are several entries in the table but none of them have a location date. Any ideas why this location date is not getting populated? On Thursday, September 8, 2016 5:02 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: Two possibilities to check: 1. That each Cataloging (collection object) record has a related Movement record; and 2. That in each related Movement record, these two fields both contain values: Current Location and Location Date. Note that the latter is also required: any related Movement records without a Location Date won't be included in the calculation of the current location, as the date that the object was (last) at that location is unknown/ambiguous. Aron P.S. Although this shouldn't affect database queries, I seem to recall having run across instances in CollectionSpace's UI, where it was necessary to refresh (or leave and then visit once again) the Cataloging record, to be able to view the updated Computed Current Location value. On Thu, Sep 8, 2016 at 3:39 PM, toolhater <toolhater@yahoo.com> wrote: Hi guys, I've noticed that the computer current location in collection objects_common is not getting updated, All the items I have in that field are blank and they do have locations assigned to them. Has anyone seen this before or does anyone have any hints why this is not working in my fcart clone? ______________________________ _________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace. org/mailman/listinfo/talk_ lists.collectionspace.org

> Sorry I've been out but I'm looking at your instructions to check the common_movements table. There are several entries in the table but none of them have a location date. Any ideas why this location date is not getting populated? The Location Date field reflects a moment in time (e.g., a timestamp) at which an object is asserted to be present at a specific Storage Location. Because such assertions typically reflect human observation, this field's value isn't automatically populated in the course of creating records: it must be entered manually, in the Location/Movement/Inventory record within the CollectionSpace user interface, or supplied as part of the data in L/M/I (aka Movement) records that are programmatically created via the Imports Service, a REST API Create call, etc. Does that help? Or might your question be different than the one this explanation is addressing? On Tue, Sep 13, 2016 at 2:41 PM, toolhater <toolhater@yahoo.com> wrote: > Sorry I've been out but I'm looking at your instructions to check the > common_movements table. There are several entries in the table but none of > them have a location date. Any ideas why this location date is not getting > populated? > > > > On Thursday, September 8, 2016 5:02 PM, Aron Roberts < > aron@socrates.berkeley.edu> wrote: > > > Two possibilities to check: > > 1. That each Cataloging (collection object) record has a related Movement > record; and > 2. That in each related Movement record, these two fields both contain > values: Current Location and Location Date. > > Note that the latter is also required: any related Movement records > without a Location Date won't be included in the calculation of the current > location, as the date that the object was (last) at that location is > unknown/ambiguous. > > Aron > > P.S. Although this shouldn't affect database queries, I seem to recall > having run across instances in CollectionSpace's UI, where it was necessary > to refresh (or leave and then visit once again) the Cataloging record, to > be able to view the updated Computed Current Location value. > > On Thu, Sep 8, 2016 at 3:39 PM, toolhater <toolhater@yahoo.com> wrote: > > Hi guys, I've noticed that the computer current location in collection > objects_common is not getting updated, All the items I have in that field > are blank and they do have locations assigned to them. Has anyone seen this > before or does anyone have any hints why this is not working in my fcart > clone? > > > > ______________________________ _________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace. org/mailman/listinfo/talk_ > lists.collectionspace.org > <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> > > > > >