Overview
The BLM needs specific data to be able to Quality Assure our index. To provide them with this data we need to pull data from both our index and LR2000. This short guide will cover this data gathering and database setup process.
Required Files
- cdi_table_for_qa.py - Creates and populates the intermediary database with data from the Kapala Index and LR2000 tables. Joins this data and exports it to a .csv file.
- qa_db.sqlite - Intermediary database used for the purposes of gathering and joining the Index and LR2000 data.
- image_data.csv - Export file containing the joined data needed for BLM QA.
- IndexQA.accdb - The Index QA database where BLM will perform their Quality Assurance.
Updating the Data Pull
The data being pulled from the Index and LR2000 tables is going to be different every time as we need to only pull data for the newest images to be indexed. To update how this data is pulled we need to make a quick change to the cdi_table_for_qa.py file.
In the CONSTANTS section of the file we need to update the DATE_CONSTRAINT constant. The value we want to place in this string is the date on which we last created CDI data for BLM QA. The last time we created this data we pulled information on all images that were indexed after our previous DATE_CONSTRAINT. Since we do not want to pull these images again we need to set the DATE_CONSTRAINT to that same day we pulled that data so that only newly indexed images will be included. Remember, this date must be in the YYYY-MM-DD format or it will not pull the correct data.
Updating the QA Database
Once you have updated the data pull, you can run the cdi_table_for_qa.py file (using PyScripter or Python IDLE through citrix) and it will produce the image_data.csv file (WARNING: this process may take a minute or two to pull all the necessary data together. Do not interrupt this process by closing PyScripter or Python IDLE or you may end up with incomplete data. Read the PyScripter console or Python IDLE shell to determine when the tool is finished). Once you have the image_data.csv file you will want to upload it into the IndexQA.accdb Access Database.
To do so, follow the steps below:
- Run the Reset Image Data query.
- Open the IndexQA.accdb file, click on the External Data tab near the top left, and within the Import & Link section select Text File.
- On the first page of the wizard, press Browse. Navigate to and select the image_data.csv file. Make sure Append a copy of the records to the table is selected and the table listed in the drop down is Image Data. Press Next.
- On the second page, select Delimited. Press Next.
- On the third page, select Comma and make sure the Text Qualifier is the quote character ("). Press Next.
- On the fourth page, press Finish.
Now that the data is imported, we need to make a couple more updates before we can pass it on for BLM QA. Follow the secondary steps below:
- Run the GetUniqueCases query. This will populate the UniqueCases table and allow cases to be selected via the drop-down on the QA form.
- Run the UpdatePaths query. This will create hyperlinks to every image so they can be easily opened.
Troubleshooting
During regular use, the user may run into certain issues.
Below is a list of commonly experienced problems and how to go about fixing
them.
Form Buttons Don't Appear to be Working
This is usually a trust center issue. Follow the steps below
to solve it.
- Using the Microsoft Access Menu go to File >
Options.
- The pop-up options window will have a menu on
the left side. At the bottom of this menu is the label Trust Center. Click
this.
- On this page, press the Trust Center Settings
button.
- The Trust Center window will now open. On this
window’s menu, click on the Trusted Locations label.
- On this page, press the Add new location button.
- On the new window, press the Browse button.
- Browse to the folder in which the HIUD Access
Database is located and select it. To be safe, you can also check the
‘Subfolders of this location are also trusted’ checkbox before pressing the OK
button.
- Press OK on the remaining two windows and then
close and reopen the entire database to refresh the trust settings.
- The form buttons should now work.