You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the migrator converts a location entry from Archon into a top container (or multiple top containers) and a linked location in ASpace, it copies the data found in the "extent" field for the location (e.g., 0.9 cubic feet) into the "notes" field in the top container record. This removes the ability of archivists to run meaningful reports on this field, but more importantly is highly misleading if the top container originated from a location entry describing more than one box (though this should be less common once we have all/nearly all of the boxes with barcodes in Archon).
For example;
In Archon:
Content: 1-3
Extent: 0.9 cubic feet
In ASpace:
1st top container:
Indicator: 1
Note: 0.9 cubic feet
2nd top container:
Indicator: 2
Note: 0.9 cubic feet
3rd top container:
Indicator: 3
Note: 0.9 cubic feet
This is very confusing since each of the boxes 1, 2, and 3 would likely be only 0.3 cubic feet each (though they could also be 0.2, 0.3, and 0.4 cubic feet). It would be better to have the note (since it is a note!) provide context, such as: "Described as content 1-3 with extent 0.9 cubic feet in Archon" (for cases where the tool is splitting into multiple top containers like this).
The text was updated successfully, but these errors were encountered:
When the migrator converts a location entry from Archon into a top container (or multiple top containers) and a linked location in ASpace, it copies the data found in the "extent" field for the location (e.g., 0.9 cubic feet) into the "notes" field in the top container record. This removes the ability of archivists to run meaningful reports on this field, but more importantly is highly misleading if the top container originated from a location entry describing more than one box (though this should be less common once we have all/nearly all of the boxes with barcodes in Archon).
For example;
In Archon:
Content: 1-3
Extent: 0.9 cubic feet
In ASpace:
1st top container:
Indicator: 1
Note: 0.9 cubic feet
2nd top container:
Indicator: 2
Note: 0.9 cubic feet
3rd top container:
Indicator: 3
Note: 0.9 cubic feet
This is very confusing since each of the boxes 1, 2, and 3 would likely be only 0.3 cubic feet each (though they could also be 0.2, 0.3, and 0.4 cubic feet). It would be better to have the note (since it is a note!) provide context, such as: "Described as content 1-3 with extent 0.9 cubic feet in Archon" (for cases where the tool is splitting into multiple top containers like this).
The text was updated successfully, but these errors were encountered: