correspsearch / cmif-creator Goto Github PK

The validation of the field for GeoNames-URIs should not only allow http:// links but also https:// (if pasted from elsewhere).

If you load a file, the license information gets lost.

I want to set date when uncertain attribute

• went into CMIF Creator
• set value
  
• saved json file
  
  
  • which timezone is active on your machine, export was performed at 2020-07-22 07:16:21
• to my surprise attribute evidence has value conjecture set
  I expected attribute cert with value low
  
• save xml file
  
• to my surprise attribute evidence has value conjecture set
  I expected attribute cert with value low
  

just for fun, tried the other way too

• CMIF Creator is showing data different as data
  
  

please find xml and json files

CMIF_Creator_20200723.zip

Neue Funktionen, um die Erfassung von Briefwechseln zwischen zwei Personen zu erleichtern:

• Weiteren Datensatz basierend auf dem aktuell erstellten hinzufügen (okay, das Label besprechen wir nochmal ;-))
• Absender- und Empfängerangaben (Person, Ort und Datum zusammen) vertauschen (Schaltfläche vlt. tatsächlich zwischen linker und rechter Spalte)
• evtl. kann man beide Aktionen nochmal in einer dritten Aktion kombinieren, die auch über Schaltfläche unterhalb des aktuellen Datensatzes ausgewählt werden kann=

Dates are restricted to be lower than 1999-12-31.
Dates after 2000-01-01 should work also!
On the other hand '0000' is accepted, also it isn't a valid date.

Please update the use API for JSON2XML from https://correspSearch.net/api/v1.1/converter/json2xml.xql to https://correspSearch.net/api/v1.2/converter/json2xml.xql (1.1 to 1.2) in the next release.

Hi!

on the correspSearch website: https://correspsearch.net/en/participate.html there's a box with:
"CSV to CMIF with Python script

Klaus Rettinghaus has developed a Python script that converts CSV tables into CMIF files. The script and the manual can be found on the GitHub account of the SAW-Leipzig.

SAW Leipzig now also offers a corresponding webapp that enables the transformation online. [To the CSV2CMI webapp]"

but Klaus Rettinghaus in this issue: saw-leipzig/csv2cmi#65 says:
"This project is not connected to https://github.com/correspSearch and the generated XML files are not suitable for use in the CMIF-Creator."

What are the tools and the supported CMIF format suited to upload correspondences in correspSearch? Is CMIF the only available format?

Thanks!

In step 4, when I uncheck "Download as JSON", the "Save" button isn't working anymore. If JSON is the only format to be offered, then the checkbox is unnecessary. However, the manual (https://correspsearch.net/index.xql?id=participate_steps) says, "you can save your CMIF file as XML". Either the save form or the manual should be updated.

I haven't found any information on how to handle non-gregorian calendar dates. I suggest to explicitly require in the manual and the documentation that all dates must be converted to the gregorian calendar (to make it conform to ISO 8601).

<email> is not mandatory in <editor>, but without it, the file doesn't load properly (editor text is lost).

... gibt z.B. 2023-06-31 aus ... das kann ja nicht stimmen. Mal checken ...

The exported file is missing the <idno>.

When I select "CC0" as license, the generated link in the CMIF file, "https://creativecommons.org/licenses/by/null/", is dead. Perhaps "https://creativecommons.org/publicdomain/zero/1.0/" would be a better option.

There seems to be a problem with names containing the character & (for example in names of companies as in Gebrüder Bla & Blub). Exporting CMIF data with such names only works with JSON, no XML export is possible. In the case of importing, XML-based CMIF data containing the name encoded with the entity & cannot be loaded with the CMIF creator.

As reported from a user:

Wir haben in unserer Edition viele Absender, deren Firmennamen nach dem Schema "Firma Blabla & Co." oder "Gebrüder Bla & Blub" aufgebaut sind. Nachdem wir alle dieser Namen im CMIF-Creator eingetragen hatten, ließ sich das Briefverzeichnis nur noch als Json, jedoch nicht mehr als XML-Datei ausgeben. Durch herumprobieren haben wir dann herausgefunden, dass es am Zeichen & lag, dass vom CMIF-Creator wohl nicht als String behandelt wird. Unser Workaround war nun, die Json-Datei herunterzuladen, die & durch einen beliebigen String zu ersetzen, das ganze wieder in den CMIF-Creator zu laden und schließlich als XML-Datei ausgeben zu lassen. In der XML-Datei selbst haben wir dann die beliebigen Strings durch & ersetzt. Nun ist die Datei vorerst fertig, allerdings kann sie auch nicht mehr in den Creator geladen werden.

This description makes it quite clear, that there is a problem with the handling of the & character for xml serialization/deserialization and also JSON import. We should check if this also happens for other XML entities such as <, > and so on.

A sample (XML) CMIF file is available if needed (I haven't attached it here yet, because I think it's not yet published).

When a file is imported where the title carries multiple attributes, these will appear in the title field as JSON. Only the text() should be considered.

Example input:

<titleStmt>
    <title xml:id="titleID" type="main">Test</title>
    <editor xml:id="editorID">Erika Mustermann</editor>
</titleStmt>

leads to:

{  "xml:id": "titleID",  "type": "main",  "#text": "Test"}

In step "3: Letter records", there is a field labelled "URL to CMIF file" ("URL zur CMIF-Datei" in German), but I think it is meant to say "URL to the letter"/"URL zum Brief".