The FOM business team is requesting access to FOM data, including standard FOM attributes, comment count statistics, and spatial object statistics. This data is needed by late January at the latest for a short-term need, and is likely needed on a quarterly basis going forward. The primary immediate business purpose of this data is to help respond to questions about the reported lack of public comments for some FOMs.
Multiple solutions are possible. For this ticket, we're looking at doing some sort of manual data extract in CSV format to meet their immediate needs and validate that we are providing the right data. In a subsequent ticket we can look at providing a longer-term solution (*)
Data attributes/statistics required (**):
- FSP ID
- Forest Client
- District
- FOM Name
- Count of comments
- Count of comments per resolution category
- Count of spatial objects (overall and/or by type)
- Overall spatial area (bounding box?) covered by these spatial objects
The business also asked for additional attributes (like type of tenure, something like that) that appear to be available in FSPTS, but isn't available in FOM. So for this we're just planning to provide the FSP ID of each FOM, and the business will need to join with FSPTS data to get these other fields.
(*) Longer-term solutions could include allowing business to pull a data extract via the FOM API, or to email out an extract periodically to the business, or more fancy building a BI / analytics environment that users can access.
(**) We will likely provide other attributes that are easy to provide, like FOM ID, created date, comment open/close date, etc.
The FOM business team is requesting access to FOM data, including standard FOM attributes, comment count statistics, and spatial object statistics. This data is needed by late January at the latest for a short-term need, and is likely needed on a quarterly basis going forward. The primary immediate business purpose of this data is to help respond to questions about the reported lack of public comments for some FOMs.
Multiple solutions are possible. For this ticket, we're looking at doing some sort of manual data extract in CSV format to meet their immediate needs and validate that we are providing the right data. In a subsequent ticket we can look at providing a longer-term solution (*)
Data attributes/statistics required (**):
The business also asked for additional attributes (like type of tenure, something like that) that appear to be available in FSPTS, but isn't available in FOM. So for this we're just planning to provide the FSP ID of each FOM, and the business will need to join with FSPTS data to get these other fields.
(*) Longer-term solutions could include allowing business to pull a data extract via the FOM API, or to email out an extract periodically to the business, or more fancy building a BI / analytics environment that users can access.
(**) We will likely provide other attributes that are easy to provide, like FOM ID, created date, comment open/close date, etc.