Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

automatic roster update workflow #37

Open
caver456 opened this issue Jun 2, 2019 · 2 comments
Open

automatic roster update workflow #37

caver456 opened this issue Jun 2, 2019 · 2 comments

Comments

@caver456
Copy link
Contributor

caver456 commented Jun 2, 2019

  1. get a standardized location or other standardized file pattern in sharepoint to download from
  2. do the automatic download from the app
  3. convert from xls or xlsx to csv in the app - use xlrd? https://stackoverflow.com/questions/9884353/xls-to-csv-converter
@caver456
Copy link
Contributor Author

caver456 commented Oct 5, 2019

now that we have an API, maybe host the roster on the server and have the clients check for and download it. Would need to have some timestamp on each one, and clients could compare, and tell the host which roster they used. Also allow multiple rosters (for different agencies).

@caver456
Copy link
Contributor Author

This is working - Steve added the script on the server that grabs the roster from D4H once a day and saves it in the 'roster' table of SignIn.db, and a corresponding API call was added so nodes can grab the latest roster from the cloud server then save it as a local .json file; on each node, the node only actually uses roster data from the .json file.

Remaining items to clean up before closing this ticket:

  • show the node admin what the date of the json file is, i.e. when it was grabbed from the cloud server, and also show the number of entries or such
  • add inline docs and header in the cloud server script and include it in the repo (do we want a separate repo only for the server? probably so! In that case push.py could be in that repo too)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant