Indeterminate number of objects now not properly located

Description

Some number of collectionobjects are not getting their correct computedcurrentlocation (and perhaps computedcrate locations?) set in the collection object record.

While this error is "recoverable", at least for a while, since the "correct" LMI and relations exist, webapps and perhaps other components that use these computed values will not work correctly.

---------- Forwarded message ---------- From: John B. LOWE <jblowe@berkeley.edu>
Date: Thu, Aug 1, 2013 at 9:24 AM
Subject: Re: [cspacedeploy] CSpace question
To: "cspace-ucb-deployments@lists.berkeley.edu" <cspace-ucb-deployments@lists.berkeley.edu>
Cc: Michael Black <mtblack@berkeley.edu>

Teammates,

The relevant cataloging record here is:

http://pahma.cspace.berkeley.edu:8180/collectionspace/ui/pahma/html/cataloging.html?csid=4583edf4-ca1d-4add-a6b3-9940c70c5f4d

...and yes it still shows the previous location as the computed
current location.

The relevant LMI record (i.e. the one that reflect the actual location) is:

http://pahma.cspace.berkeley.edu:8180/collectionspace/ui/pahma/html/movement.html?csid=1372de28-cf05-4793-9c7f

There are 11 objects associated (last edit date 7/26/13), and the 3-4
I spot-checked also do not reflect the current location.

Even if this problem is now resolved by the recent efforts, there are
probably some number of objects for which the batch process did not
get run and still show a previous location?

John

On Thu, Aug 1, 2013 at 9:17 AM, John B. LOWE <jblowe@berkeley.edu> wrote:
> Hi Alicja,
>
> When you say "updating storage locations", are you using one of the
> webapps or the regular UI to do the updating?
>
> Thanks,
>
> John
>
> On Thu, Aug 1, 2013 at 9:02 AM, Michael Black <mtblack@berkeley.edu> wrote:
>> Hi Alicja,
>>
>> A similar problem was reported two days ago and it seems to be related
>> to a recent upgrade of CSpace code. The CSpace team is working on resolving
>> that issue, but just in case this isn't the same issue, I'm cc'ing the
>> CSpace team.
>>
>> Thanks for letting me know,
>>
>> Michael
>>
>>
>> On Thu, Aug 1, 2013 at 8:55 AM, Alicja Egbert <aegbert@berkeley.edu> wrote:
>>>
>>> Hi Michael,
>>>
>>> While updating storage locations, I see that not all of my updates are
>>> reflected in the "Current storage location" field. For example, several
>>> days after I updated the location of 13-1303kk, its previous location still
>>> shows up in that field as "current." I'm wondering why, as I haven't done
>>> anything differently, so perhaps you know. In any case, I would appreciate
>>> your feedback.
>>>
>>> Thanks.
>>> Alicja
>>>
>>>
>>> Alicja Egbert
>>> Media Collections Manager
>>> Phoebe A. Hearst Museum of Anthropology
>>> University of California - Berkeley
>>> 103 Kroeber Hall, Berkeley, CA 94720-3712
>>> Tel: +1 510 642 6842, Fax: +1 510 642 6271

Environment

None

Assignee

Ray Lee

Reporter

John Brandon Lowe MLIS PhD

Labels

CC

Michael T. Black
Ray Lee
User known
User known

Task Order

None

Fix versions

Affects versions

Priority

Critical
Configure