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

Pass raw event values to front-end css #244

Open
bcipolli opened this issue Dec 30, 2015 · 4 comments
Open

Pass raw event values to front-end css #244

bcipolli opened this issue Dec 30, 2015 · 4 comments

Comments

@bcipolli
Copy link
Collaborator

Currently, the event information is combined somewhere else (server-side?) and sent to the front-end
image

@bigfleet
Copy link
Contributor

bigfleet commented Jan 4, 2016

@bcipolli
Copy link
Collaborator Author

bcipolli commented Jan 4, 2016

Yep. Sadly, the HTML generation code must be found within the middleware that pulls data into the database; by the time it gets to Ruby or the JS front-end, it's a HTML blob already. This makes it quite tenuous to reformat in the front-end (hence the retracted PR).

@bigfleet
Copy link
Contributor

bigfleet commented Jan 4, 2016

I'm going to point to this "request for comment" type page:, since this is something I'm certainly open to. https://github.com/codeforamerica/citygram/wiki/GeoJSON-Enhancements

@dsummersl
Copy link
Contributor

Following up on the RCP type page WRT opensandiego/open-dsd-notifications#15 and #247:

I think to fix issues around links/text the publisher format needs to separate out the concepts publishers are using now:

  • title: a text summary of the event without street, link, or date information.
  • href: a link to the original event.
  • address: a human readable rough address.
  • created: timestamp when the event was created in some version of ISO8601

Perhaps using some derivation of the permitdata.org the open311 specs would be helpful. Looks like they both have concepts like...

  • description: a fuller description of the event.
  • durations: what time period the event covers start to finish.
  • contact: an email to reach out to regarding the particular event.

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