Do you want your lexicon to be accessible in Karp? We are open to new collaborations, especially if the data is open. Contact us at sb-karp@svenska.gu.se.

Before you start, please consider the following:

Adding an existing resource to Karp:

• Make sure that the document is be well-formed and preferably in (valid!) JSON or LMF.
• Which fields should be visible in the graphical user interface, what should they be called...?
• Do some fields have values chosen from a closed set?
• Do you want the resource to be exported? In what format?
• If possible, provide us with a data structure specification (see below).

Creating a new resource that will be added to Karp

• If possible choose JSON or LMF format. Make sure the data is well-formed.
• Which fields should be visible / searchable in the graphical user interface, what should they be called?

Getting a copy of an existing lexicon (e.g. create a new lexicon which is identical to SweFN)

• Should some fields be removed?
• Are there any additional fields?
• Should there be any existing example entries?

General information and things to consider

• Is the lexicon, or any part of it, copyright protected?
• Who is responsible for the lexicon? Who is responsible for adding new users to the system?
• Should the lexicon be editable?
• Should the lexicon be hidden from non-authorized users?
• Is there any meta data or user info we should include on the Karp page?
• How much support from Språkbanken will be needed once the lexicon is available in Karp?
• Should there be any methodological support in the interface (e.g. auto completion)?
• Are there any references or links between entries? Are there clickable values? What behaviour is to be expected?
• Are there any references or links to other lexicons?
• Are there any references to Korp?
• Will there be any pictures or maps in the resource? Are there any specific requirements for the statistics page?

Questions? Send an email to sb-karp@svenska.gu.se

Example data structure specification:

  {
    "val1": list of strs,  Shown as "Baseform”, searchable
    "cat": int,        Shown as "cat value”, not searchable, hidden in exported version
    "dog": int,        Shown as "dog value”, clickable, searches for similar dog values
    "senseid”: str     Shown as "Saldo sense”, clickable, links to SALDO
  }