Open jadudm opened 2 years ago
This probably assumes a lookup table for devices. What needs to be stored for each device?
The fcfsID already has state information and... something else? In the naming convention. Would we want to associate it with any other information? MAC address is separate from this ID.
City/County? Timezone or Lat/Long? Serial Number, Creation date?
At the very least, I'd like an ID and State (though we can infer the later from the ID if necessary).
Great points!
Yes, we have a "heartbeat" table planned where we can store this kind of metadata. Like device type (Windows, Raspberry Pi, etc) and its associated FSCS id. We could also enter ignored MAC addresses in there.
Other than that, library data is open so we can either replicate or (my preference) look up on demand. For instance, https://www.imls.gov/search-compare/details.html?fscs_id=GA0027 gives you the library data for that specific FSCS -- probably way more data than we want/need but it's all there, hopefully.
The data is already present or can be derived, I guess the question is -- which bits of information do we need/want to show users?
Oh I really like that there's already a way to look up library data on imls.gov. Will we need a separate API key for that? I agree, that seems preferable.
Seems like we'd only need to store device-specific information, then. Hardware stuff :)
Background
Libraries might want to filter out devices that they know are "theirs," and should not appear in the data.
It covers the following stories:
We'll know we're done when...
Questions