Submitting
Right now, it is best to run each of these locally with each queue enabled one at a time
Start by sending a request to http://localhost:7297/api/generate/hs/[graduates|request]
Then, on at a time, set to false and run debug the application:
– AzureWebJobs.MetaQueue.Disabled
– AzureWebJobs.ProcessFileGeneration.Disabled
– AzureWebJobs.HighschoolFileConsolidation.Disabled
This function app should probably be re-written to take advantage of a session-ed service bus queue and possibly an append blob (instead of write blob) so that multiple instances can write at the same time. Additionally, how it determines which id’s to send needs to be optimized.
One possible way it could be optimized is to take into account (if not already) the NSWERS IDs already in the NSC data tables in RDB when retrieving the list of NSWERS IDs to process. Still need to keep the check to see if they are in the local NSC database to make sure they haven’t been sent but no response yet loaded into RDB.
Graduates File
These are students that exited a Nebraska HS with a 210 or 211 exit code but do not show up in a Nebraska Public Post Secondary institution, excluding those previously submitted.
GET: https://fnnsc.azurewebsites.us/api/generate/hs/graduates
Requests File
These are students that exited a Nebraska HS with a non-graduation exit code (202, 208, 209, 212) that are in K12, but do not show up in postsecondary data sources, excluding those previously submitted.
GET: https://fnnsc.azurewebsites.us/api/generate/hs/request
Receiving
Leave a Reply