Consider adopting open data standards

[ctorgalson]

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 from Thing 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?

[willguv]

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.

[andybroomfield]

I think localgov_news does add the schema metadata module.

[willguv]

That's good to know, thanks @andybroomfield

[ctorgalson]

I think localgov_news does add the schema metadata module

schema_metatag does include JobPosting, so we could follow that pattern :+1:.

[markconroy]

I'd like to see us creating an independent module for localgov_metadata or something like that, so we don't have a few different modules all add the same metatags and schema_org modules etc.

That module can set up the base metatags that all content types can use. Then the job vacancies module can just add what it needs.