Update all records that contain resources which are missing the resource_storage_location field.

[dkelsey]

TASK

since the 1.7 release resource_storage_location has been a mandatory field. Records the pre-existed the release did not contain a value for this field (*)

* some actually did. Why? How?

Some records have more than one resource which omits this field. With that condition, the user interface will not allow editors to update their record:

• update one resource by adding the field, and updating will attempt to update.
• The catalogue application (GUI/APP) checks/assertions will find the other resources in the record and check each of them; it will find the other resource which is missing the field and silently do nothing.

The task is:

Write a one-off script to add/set the resource_storage_location field for resources where this field is missing, and update all records that contain these resources.

[dkelsey]

I ran my script after some analysis and testing. I backed-up each record to a JSON file before making the update.

• 439 Metadata records were updated
• 735 Resources were updated.

Every resource in every metadata record now has a resource_storage_location field.

My analysis was to see how difficult it would be to set the values correctly. The current breakdown of resource_storage_location:

Label	Count
External	2694
BCGW Data Store	2343
Catalogue Data Store	1179
EDC Data Store	769
BCGW DataStore	434
BC Geographic Warehouse	260
Web or FTP Site	191
Pub.data.gov.bc.ca	147
Ministry or Other Database	21
Esri ArcGIS Onlin	20
File System	8
Unspecified	6

Note:

• The correct location for BCGW resources is “BC Geographic Warehouse”; many resources have the wrong values for this.
• The correct location for BCDC resources is “Catalogue Data Store”; many resources have the wrong value for this.
• “Unspecified” does not mean Null or empty; it is the string “Unspecified”