...
TMS table name | TMS field name | CSpace field name | notes |
|---|---|---|---|
ObjLocations | Handler | locationHandler | Constituents FK LocHandlers FK ObjLocations.Handler |
ObjLocations | LocationString | displayName currLocation | FK Locations.LocationID |
ObjLocations | ObjectNumber | objectNumber | ObjComponents FK Objects FK ObjComponents.ComponentID |
ObjLocations | TransDate | Timestamp locationDate | Needs to become a real timestamp in CSpace |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
SELECT j.ObjectNumber objectNumber, l.LocationString displayNamecurrLocation, o.Handler locationHandler, o.TransDate TimestamplocationDate, p.LocPurpose reasonForMove, o.AnticipEndDate plannedRemovalDate, o.DateOut removalDate, o.Sublevel+o.SearchContainer+o.TempText+o.Approver+str(o.CrateID) currentLocationNote, l.LocationID locationShortID, (case when o.Inactive = 1 then 'active' else 'deleted' end) miscStatus FROM ObjLocations o JOIN Locations l ON l.LocationID = o.LocationID JOIN Objects j ON j.ObjectID = o.ComponentID JOIN LocPurposes p ON p.LocPurposeID = o.LocPurposeID ; |
...
- Perhaps the barcode process should also use the notes field? Perhaps And perhaps some details of the scanner being used might be included?
- I noticed elsewhere that the barcode scanner seems not to be 100% accurate (sometimes the scanned items was incomplete or missing). Perhaps something could be included in the file to help detect this?
- MB suggests that perhaps "inactive" records be included, and a "soft delete" perfomed performed on them. This makes sense, I think, in which case we would want to map that field to whatever CSpace uses to mark a deleted record.
...