History for Metadata Tagging

changed:
-There are several ways to talk about or record geographic locations at MIT. MIT Facilities data is managed using coordinates based on the Massachusetts State Plane coordinate reference system using NAD 27 feet. (What's the EPSG code for this?). Let's call these MITGeoCoords for now. MIT people use either Building/Room (e.g. N52-200), official names (e.g. MIT Museum), or unofficial names (e.g. Infinite Corridor - is that really unofficial?).
There are several ways to talk about or record geographic locations at MIT. MIT Facilities data is managed using coordinates based on the Massachusetts State Plane coordinate reference system using NAD 27 feet. (What's the EPSG code for this?). Let's call these !MITGeoCoords for now. MIT people use either Building/Room (e.g. N52-200), official names (e.g. MIT Museum), or unofficial names (e.g. Infinite Corridor - is that really unofficial?).

changed:
-Often the precision of the specified coordinates will not match the precision of the thing being tagged. Using a designation such as 7-100LA (Lobby 7) talks about a very large area. It includes the kiosk on the North side as well as the Boswells cafe seating on the South side. In this case, using MITGeoCoords could be more precise. However most people will not know the MITGeoCoords for a specific spot. The opposite problem can also be true. If you're talking about Lobby 7 and use an MITGeoCoord to pin down an exact spot, that might not be the actual spot you mean, or you might be talking about the entire lobby rather than a specific spot. Thus we also need to capture an "intended precision" indicator.
Often the precision of the specified coordinates will not match the precision of the thing being tagged. Using a designation such as 7-100LA (Lobby 7) talks about a very large area. It includes the kiosk on the North side as well as the Boswells cafe seating on the South side. In this case, using !MITGeoCoords could be more precise. However most people will not know the !MITGeoCoords for a specific spot. The opposite problem can also be true. If you're talking about Lobby 7 and use an !MITGeoCoord to pin down an exact spot, that might not be the actual spot you mean, or you might be talking about the entire lobby rather than a specific spot. Thus we also need to capture an "intended precision" indicator.

changed:
-2. Actual MITGeoCoords for the type
2. Actual !MITGeoCoords for the type