Add a field and code explorer

[jpmckinney]

From @ColinMaudry in open-contracting/infrastructure#163

I think a field database bound to a multilingual glossary of terms would greatly help. Fields could be tagged and categorized according to various properties such as:

• OCDS version compatibility
• core or extension
• update date

Full text search would enable discovery via keywords... especially if synonyms are documented in the glossary for keyword equivalency!

With the EU extensions alone, I think a similar tool would greatly increase the visibility of the semantics and structures available for OCDS adopters.

Also relevant to #891

[jpmckinney]

We can maybe start with a simple widget using https://select2.org or similar that allows people to search fields/codes by name, title and description. Other ideas:

• Airtable-based tools

[jpmckinney]

Going further, besides finding a term based on its machine name, title and description, we can support finding it based on synonyms, pulled from a glossary that crosswalks to GPA, UNCITRAL, etc. (related #827).

[duncandewhurst]

This would be very useful as I frequently find I have missed fields introduced in EU extensions.

[jpmckinney]

I made a lookup for all extensions (but not core fields or codes): https://open-contracting.github.io/editor-tools/

I can add core later, but i think most editors are familiar enough with core.

Repo is here, on which we can create issues: https://github.com/open-contracting/editor-tools

The intended audience is just OCDS contributors. We would design something else for a public audience.

[odscrachel]

This is brilliant, adding the core fields at some point would be helpful.