Test Article: Metadata vs Core Data Fields
Q&A: What is the difference?
A: The terms I would wire into my brain are “Core Station Properties” or “Core Properties” and Metadata. Core properties are expected values present for every station. Most core properties are viewable on the stations API endpoint, but some are internal only. Metadata will be kept for individualized fields that are requested or we need to track.
District is a good example of a metadata field. Not all clients use it; it doesn’t live in the data tables and is not a tracked field for EVERY utility station.
Installation date is a good example of a core property, as it will be tracked for EVERY station.
Q: For Utilities that have terminal info recorded, are we still recording in the Metadata? Not currently listed to record in Core or Meta. Example SCE and their sat terminals.
A: TI-#### is a good example of a metadata field that is ALSO part of the equipment list. While TI-### is NOT a core property that exists for every station, it’s primary source should live on the specific equipment row under equipment fields. This means that eventually, this metadata field may be retired or imported and go away from the old Metadata section.
It is unclear if any currently maintained metadata fields will always remain there, as there will likely be a future home for each field we decide needs to continue to be tracked.
Q: Foresee Fire Tier and Meso being missed? Include this task in weekly deliverable? While updating on Master also update in Meta and check for tier?
A: Yes, since the current process requires you to compile new information to the Master before exporting, we should add to this deliverable to also update the old metadata section with this information. Since we haven’t necessarily maintained these two fields as part of new installs to date, we can likely generate a simple import spreadsheet, then we just need to upkeep as stations are installed as part of the weekly deliverable.
Q: Will tech support get notified in the future prior to when updates like this are put into place so that we can plan accordingly and know how to react?
A: While I would love to confirm that we will provide future preemptive updates, the reality is that we have been slowly updating the development team with a direction, and we have never had a solid game plan and firm direction/requirements to date.
I am in a weekly meeting where updates are shared, it is possible these update pages can be accessed by Tech support directly; however, the content is basic checklist of tasks and doesn’t answer detailed questions like this.
As I continue to offboard more direct oversight over tech support, I will have more time to oversee and provide more detailed direction as we go along.