-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix unique name for CivicPlus sites #80
Comments
Whoops. This is a non-issue. Was using an alternate domain for Columbus, which does indeed have a proper CivicPlus subdomain: |
It would be possible to add some logic that could devise a unique name for an asset other than its subdomain on CivicPlus. For example, given a non-standard URL such as Napa County (https://www.countyofnapa.org/AgendaCenter), we could derive the name from the base domain. However, this would pose downstream issues in code that expects the Two possible strategies that would be more robust:
We've already started down the path of manually correcting state/place data in aw-scripts because there are problems ascertaining this info even on subdomains, such as for water districts. Will likely need to use some form of the "corrections" approach here in the core framework to generate accurate, standardized place information for each site.
|
We need a more robust strategy for determining a unique name for sites/assets.
The current strategy for determining a unique ID for a site assumes a subdomain containing place-related information.
But not all CivicPlus sites have a place-oriented subdomain. For example, Napa County has a broken CivicPlus subdomain but a working AgendaCenter site on its own county domain (as of late Dec. 2020):
With the current strategy, we end up producing asset names such as below:
The text was updated successfully, but these errors were encountered: