...
| Table of Contents | ||
|---|---|---|
|
Object Inventory
...
overview
Inasmuch as the migration of the locations of objects at PAHMA (and their history) is functionally similar to the (already implemented) PAHMA + bar + code + scanner + requirements inventory process implemented to support the use of barcode readers, it has been decided to "piggyback" the TMS to CSpace migration on this process.
...
An analysis of the existing TMS data reveals that a few more fields will need to be included; the barcode process will be extended to handle these additional fields.
field mapping, basic barcode format
TMS table name | TMS field name | CSpace field name | notes |
|---|---|---|---|
ObjLocations | Handler | locationHandler | Constituents FK LocHandlers FK ObjLocations.Handler |
ObjLocations | LocationString | displayName | Storage location < StorageLocations FK Locations.LocationID |
ObjLocations | ObjectNumber | ObjectNumber | ObjComponents FK Objects FK ObjComponents.ComponentID |
ObjLocations | TransDate | Timestamp | Needs to become a real timestamp in CSpace | Fields
fields to be added to barcode format
TMS table name | TMS field name | CSpace field name | notes |
|---|---|---|---|
LocPurposes | LocPurpose | Reason for move < LocPurpose (text) |
|
ObjLocations | AnticipEndDate | Planned removal date |
|
ObjLocations | DateOut | Removal date |
|
ObjLocations | concat(Sublevel, SearchContainer, TempText, Approver) | currentLocationNote | |
ObjLocations | CrateID |
| (not sure where to map this in CSpace yet...) |
...
Note from MB, saved for posterity
| Code Block |
|---|
---------------------------- Original Message ----------------------------
Subject: Storage location fields and barcode inventory fields
From: "Michael T. Black" <mtblack@berkeley.edu
Date: Thu, January 26, 2012 4:14 pm
To: jblowe@berkeley.edu
--------------------------------------------------------------------------
First, here are the fields produced by barcode inventory:
* Person's name
* Storage location
* Object number
* Timestamp
And here are the fields we'll need to import from ObjLocations:
* Handler (will give Person's name, when used as FK to LocHandlers and then to
Constituents)
* LocationID (will give Storage location when used as FK to Locations.LocationID)
* ComponentID (will give Object number when used as FK to ObjComponents and then to
Objects)
* TransDate (will serve as Timestamp)
* LocPurpose (to "Reason for move")
* CrateID
* AnticipEndDate (to "Planned removal date")
* DateOut (to "Removal date")
Need to go somewhere:
* Sublevel (notes, some crates)
* SearchContainer (notes, some crates)
* TempText (notes, some reasons)
* Approver (notes, some reasons)
Not clear whether useful in CSpace:
* Inactive (is working as a sort of soft delete)
Not needed in CSpace:
* TempFlag
* LoginID
* EnteredDate
* TempTicklerDate
* LocLevel
* PrevObjLocID
* NextObjLocID
* SchedObjLocID
* RequestedBy
* ShipmentID (at least not needed now/soon)
* TransStatus (at least not needed now/soon; 1=completed; 2=pending)
|