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

OpenGrid update 311 datasets to reflect SalesForce Service Platform (open data update) #334

Closed
6 tasks done
reve0716 opened this issue Feb 11, 2019 · 13 comments
Closed
6 tasks done
Assignees

Comments

@reve0716
Copy link
Contributor

reve0716 commented Feb 11, 2019

311 data has been updated with Salesforce as a service platform. Our open Data Portal reflect these changes. We need to reflect those same alterations within OpenGrid. Here are the steps to implement this transition.

  • 1. Jonathan to configure Open Data Portal data-set.
  • 2. Jonathan submit dataset to Plenario
  • 3. Open Grid Team to identify each 311 data-sets that needs to be update in OpenGrid. 311 data-set in OpenGrid is broken into segments as the open data portal.
  • 4. Vince (Plenario) to implement the data-set after step 2.
  • 5. EKI to configure after step 3.
  • 6. Regina to test the data-sets.
@reve0716
Copy link
Contributor Author

consult with vince how the new items that will be available in future affect vince process on plenario side.

@reve0716
Copy link
Contributor Author

Vince approved Jonathan request for new 311 dataset. Next is to load the data in plenario.

@reve0716
Copy link
Contributor Author

reve0716 commented Apr 8, 2019

@rladines 311 saleforce data has uploaded into plenario, need to be configure to OG.

@rladines
Copy link
Collaborator

@reve0716 Is the expectation to keep all existing 311 broken out datasets and include an all-encompassing one called "311 Service Requests" (maps to plenar.io dataset called 311_service_requests) like below?

image

@reve0716
Copy link
Contributor Author

@rladines in terms of the broken out data-set those would be considered legacy data with an exception to abandoned vehicles which is bringing in current data. To answer your question we can include the 311 Service Requests (311_service_requests) and keep the existing ones since its historical data but we need to identify those data-sets as historical. I test to identify if all are returning current or data from 2018.

@rladines
Copy link
Collaborator

@reve0716 How are we planning to distinguish the legacy 311 datasets as 'Legacy'? Can we ask Vince/Plenario to update the human_name attributes of these datasets to say Legacy e.g. "311 Service Requests - Graffiti Removal (Legacy)"?

@reve0716
Copy link
Contributor Author

@rladines sure i'll send Vince and email to update the human names attributes and cc the team.

@rladines
Copy link
Collaborator

@reve0716

The opengrid-plenario-service had been restarted.

This is how the dataset names look now:
image

@reve0716
Copy link
Contributor Author

@rladines I need to contact Vince about the abandoned vehicle dataset should not be labeled as legacy the dataset is pulling current data but overall it looks great.

@reve0716
Copy link
Contributor Author

@rladines The abandoned vehicle labeling was resolved.

@reve0716
Copy link
Contributor Author

reve0716 commented Apr 29, 2019

Created another issue about list of values not being filtered in new dataset see reference issue #339

@reve0716
Copy link
Contributor Author

reve0716 commented May 6, 2019

Closing this issue, service request dataset has been added and tested,created offside issue that relates to this dataset setup that needs separate attention.

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

No branches or pull requests

3 participants