Integrate AMD Signal Asset into SMO Artbox Location

[KaroEngstrom]

Goal: add a standardized location identifier for Artbox cabinet in the Smart Mobility app / Artbox Program

This issue is for the dev side. App side documented in #10508 Configure Artbox Location

• We should be using the 'signal ID' object for the project to connect to 'artist' object, etc. as needed
• We would need to pull the signal data from AMD Data Tracker (borrowing data from DT)
• Synced with Diana 11/28/22: she had discussed with Brian C/AMD and agreed this should connect to their Signal ID asset
• Diana will manage the item to dev product sync to discuss options

[patrickm02L]

Ask Billy's group whether we should use the signal ID or cabinet ID.

[patrickm02L]

Code reference for integration services from one Knack app to another.

[patrickm02L]

Prior to Devs doing work on this, the apps team can upload the data.

We still need to know what the name of the app is (object ID and Knack configuration details).

[dianamartin]

@KaroEngstrom - In order to do this DEV enhancement can you please:

• [x] export this signals object table
• [x] create a new object signals in the SMO app
  • we don't have to keep all fields
• [x] Update this issue with new new SMO object for the signals view

Fields to Keep

• SIGNAL_ID - short text
• ATD_LOCATION_ID - short text
• LOCATION_NAME - short text
• SIGNAL_STATUS - short text
• WEB_URL_GENERATOR_PM
• COUNCIL_DISTRICT
• SIGNAL_NAME (ex. Signal ID: Location Name)
• SIGNAL_ENG_AREA

@patrickm02L @johnclary I'm thinking if we should also import/integrate the cabinet data as well?

Useful Cabinet Info - cabinet object table

• Cabinet ID: 1
• Cabinet Type: 332
• Cabinet Corner: NE
• Signals (ex. Signal ID: Location Name) - 332: LAVACA ST / 3RD ST
• Signal ID: 332
• Location (X,Y info)
• Art Box: Yes/No
• Location Description: ex. 216 Lavaca St Austin, Texas 78701

[KaroEngstrom]

M 12/4/22

• initial artbox-signals object created and imported

[KaroEngstrom]

W 12/7/22

Required items for dev work

• New object table artbox_signals in SMO
• Application info in 1Password

Coordinating update - we are going with signals object and building on that (see object table link above). We will not be including the cabinets object. See connected issue #10508 for more details.

[patrickm02L]

Prior to Devs doing work on this, the apps team can upload the data.

We still need to know what the name of the app is (object ID and Knack configuration details).

12/21/22 In Apps Grooming. Ready for Devs to create automation that pulls in the signals new or updated data daily.

[patrickm02L]

We still need to know what the name of the app is (object ID and Knack configuration details).

We still need this. @KaroEngstrom would you be able to provide the above.

[KaroEngstrom]

@patrickm02L I tried to include everything in the 1Password entry - can you indicate what is the missing item?

Link to 1Password

[chiaberry]

This is my take on the ask: data from: Data Tracker, view_197 (signals data pub view) to: Smart Mobility, scene_146/views/view_396 (artbox locations) daily/overnight update

I see @dianamartin asked above about "I'm thinking if we should also import/integrate the cabinet data as well?". Moving forward for now with the signals data pub view as requested until we get further instruction.

[KaroEngstrom]

@chiaberry We did get confirmation from Billy B./AMD that signals_cabinets is not required. That did not get updated in this sibling issue - sorry. (#10508 )

[patrickm02L]

In data planning 1/12/23. Charlie says he needs to test it. Will shoot to be done 1/20/23.

[patrickm02L]

1/18/23 Grooming.

@KaroEngstrom will do some spot checking to see if records are up to date. Based on the ETL running the last modified date should have occurred 1/17/23. Diana says to look at 5.

[KaroEngstrom]

W 1/18/23

• a relatively new Knack feature allows us to check record history on the objects and I'm seeing successful updates by the API coming through on all the spot-checked records. Example: Signal 4141
• for the dev part, this is complete

[Charlie-Henry]

@KaroEngstrom @patrickm02L I can go ahead and refresh the dataset again if there is some missing recently updated records? Possible a couple slipped through during my testing.

[KaroEngstrom]

I don't believe anything to be missing but if you want to run a refresh, I can look on the Builder side. Thanks, @Charlie-Henry

[Charlie-Henry]

refreshed! @KaroEngstrom

[KaroEngstrom]

@Charlie-Henry Looks great, I'm seeing the updated records in Smart Mobility

[KaroEngstrom]

@Charlie-Henry @patrickm02L @dianamartin Gm, I know I closed this since it works, but: I'm drafting a note to the stakeholders and I don't know the interval for this one to update. Does this have a regularly scheduled cadence or just as needed? Or, is this something we'll need to ask the stakeholder?

And yes, I think I wrote the initial issue poorly. We had already downloaded and imported the Signal data. This item is to keep it up-to-date.

[patrickm02L]

@KaroEngstrom we don't have a cadence of check-ins with Sandra anymore. We did at the beginning, but they've become ad hoc since you backfilled the projects.

[KaroEngstrom]

@patrickm02L Right, I'm drafting that letter to close out this project. Here I'm curious about the frequency of Signal updates from Data Tracker to the Artbox application. I'm not sure an automation was set up, which is what we needed to keep the Location data up-to-date.

Got the info I needed from Patrick. Once a day, thank you!

[chiaberry]

@KaroEngstrom It currently is scheduled to run twice a day, everyday. although im inclined to see if we can make it run only once. Would daily be an acceptable cadence?

[KaroEngstrom]

@chiaberry thanks! I think daily is plenty

[Charlie-Henry]

@KaroEngstrom @chiaberry configured to just run once daily at 6:30PM 👍