Deployment Value Change Tracking/Searching/Reporting

[sbatchelder]

CI TASK21 TASK23 TASK24

Asset Management: Deployments

[sbatchelder]

I had asked @cahearn some question regarding deployment csv fields. This is his response

From a WHOI/CGSN perspective:

1. For the uid fields: sensor.uid usually correlates to RDB serial number, electrical.uid is blank everywhere right now because it is intended to give us a place to list the RDB serial number when sensor.uid. node.uid should be safe to ignore, it operates much like mooring.uid, but for a subsystem within the deployment.
2. versionNumber is always 1...
3. orbit is always blank. Removing it broke things soooo it remains
4. recoveredBy and deployedBy are not used by CGSN. Plot twist! They seem to have recently started to be used by other groups. They are people, but not necessarily RDB users or usernames
5. notes should probably be just a note in the inventory history, but not sure just yet.

That's the update I have so far. Thanks for your patience on this. We should talk more about these sometime soon.

[sbatchelder]

Update:

• Deployment Export now only exports InventoryDeployments
• sensor.uid maps-to inventory.serial number
• versionNumber always 1
• orbit always blank
• notes is inventory.detail for now, but it could also be assembly_part.note or something else. tbd.

Remaining:

• mooring.uid, node.uid, electrical.uid, are still unknown/left blank. The node and mooring are sometimes filled in the CI github csv's
• we don't have a means in rdb to record deployedBy and recoveredBy values so for now these are blank. Do we want to officially add optional "deployedBy" and "recoveredBy" fields for deployments?
• assembly_template_revision is in many (all?) deployment github CSV's, but they're all empty. Are these for the build assembly templates or assembly part revisions? Should it the full name or just the revision letter/code, or should it also jus be left blank?

[joannekoch]

@sbatchelder
The following are verified in the deployment export:

• Deployment Export now only exports InventoryDeployments
• sensor.uid maps-to inventory.serial number
• versionNumber always 1
• orbit always blank

Deployment Export exports InventoryDeployments, but also includes Inventory that are retired from a Deployment. Is this the intent?

Notes exported are not user defined notes, they are the latest event history note. Is this the intent? See below.

[sbatchelder]

Hi Joanne,

Re: notes, I couldn't tell where user notes for an inventory deployment could be so I used the latest event history note. I'm not sure if that's what's intended for the field though.

Re: "but [deployment export] also includes Inventory that are retired from a Deployment. Is this the intent?" ... I think it is? but I'm also not entirely sure what it means for something to be retired from a deployment..

@cahearn can you weigh in on these?