Add acronyms to data model

[danmichaelo]

Requirements:

• For presentation purposes, acronyms should be linked to terms
• It should be allowed to use acronyms as preferred terms or alternative terms

Example from Roald 2:

te= Hypertext markup language
bf= Dynamisk html
bf= Dhtml
bf= Xhtml
en= Hypertext markup language
ak= HTML

Roald 3 suggestion:

{
    "13819": {
        "prefLabel": {
            "en": {
                "acronymFor": "HyperText Markup Language",
                "value": "HTML"
            },
            "nb": {
                "acronymFor": "HyperText Markup Language",
                "value": "HTML"
            }
        },
        "altLabel": {
            "nb": [
                {
                    "value": "DHTML",
                    "acronymFor": "Dynamisk HTML",
                },{
                    "value": "XHTML"
                }
            ],
            "en": [
                {
                    "value": "DHTML",
                    "acronymFor": "Dynamic HyperText Markup Language",
                },{
                    "value": "XHTML",
                    "acronymFor": "Extensible HyperText Markup Language"
                }
            ]
        }
    }
}

If the acronym is not the presentation term, we could use hasAcronym instead of acronymFor.

Some manual work will be involved in matching terms to their acronyms, but there's < 500 acronyms so that's ok.

[danmichaelo]

Example using acronymFor:

    {
        "nb": {
          "value": "LVSEM",
          "acronymFor": "Low-voltage scanning electron microscopy"
        }, 
        "en": {
          "value": "LVSEM", 
          "acronymFor": "Low-voltage scanning electron microscopy"
        }