Closed bferguso closed 1 week ago
Created test insert and ran it w/ Archeology branch. Outcome is:
Was able to set contextual fields (USER IDs, creation/modification dates, createdusing = 'Arches' as part of the insert. Set the object ID to a negative number as it is unclear how the sequence number is generated.
After further consultation w/ John L, found a potential way to make this work. John L. agrees in principle to the approach we are working on (added to the description).
Features that have been created w/ the UI are temporarily stored in the SDE.A101 table (in TEST and PROD). To find the next sequence number in the borden grid we need to perform a union of the SDE.TFM_SITE and SDE.A101 tables.
Although the table in TEST/PROD is A101, it is automatically generated. To confirm/identify the temporary table that is used for this the following query can be run:
select * from sde.table_registry where table_name = 'TFM_SITE';
John L. will try to identify the oracle sequence to populate the OBJECTID column or give me access to look at the sequences.
@TMcFarland-Heritage, @BaldeepPal - would you please setup a meeting w/ security to see if there will be any issues accessing the HRIA database from our Arches application? The initial tests we have done look promising and the last steps are to ensure that we can open a port from Arches to HRIA database and then finally include the other vendor to see if there are any other issues or concerns they may have.
@bferguso looks like there was another ticket completed about the security review of this and I assume was ok. Let me know what next steps are to set up a meeting with vendor.
Have an end-to-end running in my dev environment using DB logic and FDW to connect from Postgres to HRIATST1. Currently using copies of the A101 and TFM_SITE in my personal schema.
Trying to use direct SQL to generate skeleton record in HRIA. Need to do test to see if this is possible. Things to consider:
If direct database is not possible, other (not ideal) options are:
Approach proposed:
Testing will need to be done in HRIA to ensure that this process does not cause any issues within the HRIA application.
The borden grid WFS can be used to lookup what grid we should be searching for based on the geometry of the site. Proposing that we use the centroid of the geometry to do the lookup to find the point for the following WFS request:
https://dlvrapps.nrs.gov.bc.ca/int/arches-bchp/bctileserver/geo/pub/WHSE_ARCHAEOLOGY.RAAD_BORDENGRID/ows?service=WFS&request=GetFeature&outputFormat=json&version=2.3.0&typeNames=WHSE_ARCHAEOLOGY.RAAD_BORDENGRID&cql_filter=DWITHIN(GEOMETRY,POINT(1161815%20452123),1,meters)