As a NRCED user, I want to be able to search for the requirement source using the Act and/or Regulation search tool so that I can find what I'm looking for more easily and get a more complete picture of inspection activities.
Additional Context
Currently, when a user uses the "Act" or "Regulation" search filters, they will only be able to filter down to the single Act value stored in the Legislation subset.
For NRIS-EPD inspection records, that is currently the Act or Regulation information for the legislation that authorizes the the inspection (either the Environmental Management Act or the Integrated Pest Management Act)
However, the source of the requirement (i.e. whatever law or permit that the inspector was inspecting) is usually something other than those two acts - usually it's a regulation or a permit.
Records are capable of storing multiple acts/regs in the Legislation subset - however, at the time the NRIS-EPD importer was coded, records only held one Act/Reg value.
The requirement source is currently stored in the Summary field (see screenshot)
Since then, the legislation subset was improved to hold and display multiple values for legislation/regulations - however, that additional functionality has not been implemented in importers.
A user who wanted to find out for example which facilities have been inspected for possible violations of the Recycling Regulation might select "Recycling Regulation" from the Regulation filter. However, currently that would return 0 results (see screenshot)
By contrast, a search for "Recycling Regulation" in the Keyword Search bar will yield too many results, because it will search the summary field and return both "Recycling Regulation" and "Organic Matter Recycling Regulation" matches.
By correctly listing both the authorizing legislation and the inspected requirement in the Legislation subset, a user will find the correct records using the Regulation search filter.
The screenshot below shows how the record will look once the requirement value is moved from the Summary to its own row in the legislation subset
The below screenshot shows how the user's search experience will be once the change is made.
This should be achievable by updating the code to the importers. The back-end work needed was done previously.
There are some Requirement Source values for which the import behaviour should not be modified, namely anything that is not an act or regulation. Kyle will provide a table to show how to handle the various Requirement Source values.
As a NRCED user, I want to be able to search for the requirement source using the Act and/or Regulation search tool so that I can find what I'm looking for more easily and get a more complete picture of inspection activities.
Additional Context
Currently, when a user uses the "Act" or "Regulation" search filters, they will only be able to filter down to the single Act value stored in the Legislation subset.
For NRIS-EPD inspection records, that is currently the Act or Regulation information for the legislation that authorizes the the inspection (either the Environmental Management Act or the Integrated Pest Management Act)
However, the source of the requirement (i.e. whatever law or permit that the inspector was inspecting) is usually something other than those two acts - usually it's a regulation or a permit.
Records are capable of storing multiple acts/regs in the Legislation subset - however, at the time the NRIS-EPD importer was coded, records only held one Act/Reg value.
The requirement source is currently stored in the Summary field (see screenshot)
Since then, the legislation subset was improved to hold and display multiple values for legislation/regulations - however, that additional functionality has not been implemented in importers.
A user who wanted to find out for example which facilities have been inspected for possible violations of the Recycling Regulation might select "Recycling Regulation" from the Regulation filter. However, currently that would return 0 results (see screenshot)
By contrast, a search for "Recycling Regulation" in the Keyword Search bar will yield too many results, because it will search the summary field and return both "Recycling Regulation" and "Organic Matter Recycling Regulation" matches.
By correctly listing both the authorizing legislation and the inspected requirement in the Legislation subset, a user will find the correct records using the Regulation search filter.
The screenshot below shows how the record will look once the requirement value is moved from the Summary to its own row in the legislation subset
The below screenshot shows how the user's search experience will be once the change is made.
This should be achievable by updating the code to the importers. The back-end work needed was done previously.
There are some Requirement Source values for which the import behaviour should not be modified, namely anything that is not an act or regulation. Kyle will provide a table to show how to handle the various Requirement Source values.
Acceptance Criteria