-
Notifications
You must be signed in to change notification settings - Fork 0
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
Consider adopting open data standards #15
Comments
Hi @ctorgalson thanks for finding this. We haven't used this kind of microdata elsewhere. One approach would be to canvass councils about the JobPosting schema and use a subset of its fields. I doubt they need everything. Happy to entertain other ways of doing this. The nearest example of standards use in LGD is Open Referral and @ekes @finnlewis may be able to share more. |
I think localgov_news does add the schema metadata module. |
That's good to know, thanks @andybroomfield |
|
h/t @finnlewis for asking the question and pointing the JobPosting schema.
@willguv, it looks like gov.uk prefers schema.org's JobPosting schema as well.
So given a metadata standard exists, we'd need to implement the markup and the UI for entering the data. Providing the microdata via a custom template in the module is straightforward.
W/r/t to the fields, there are a lot of potential fields to add to the CT: 35 specific to
JobPosting
plus another dozen inherited fromThing
that could be available.Has the LGD project used this kind of microdata elsewhere, and if so, how were the fields handled in the UI? Would we provide the entire set and expect implementations to enable/disable fields as needed?
The text was updated successfully, but these errors were encountered: