Imprint metadata about recogito-tei HOT 5 CLOSED

In that case, I think the user should know which elements are supported as input. Then work with Recogito to annotate entities, export and keep encoding other metadata or structural elements. At the moment, I see a problem if the user encodes certain things and then after working with Recogito s/he gains information about entities but loses information on other aspects after exporting.

from recogito-tei.

I also think that the user in Recogito should know which fields / TEI tags are available for input and export.

from recogito-tei.

Just to clarify/summarize what's available & implemented right now:

• When exporting a .txt file as TEI, a select set of metadata fields are converted to header tags - I agree we should document this somewhere.
• When exporting a .tei.xml (i.e. originally uploaded as TEI) as TEI, Recogito makes no change to whatever was in the original TEI header fields. Exporting the file will return the original header as it was
• When importing a .tei.xml file, Recogito will not parse the original header, nor pick that information up for the internal metadata (title, author, etc.) It potentially could do that (with a bit of extra development), and merge changes made in the Recogito UI back into the original TEI.

from recogito-tei.

Sorry! I had misunderstood this - thank you for the clarification @rsimon and sorry again.

from recogito-tei.

This was somehow discussed in issue #6 - we agreed to review the proposal and see if it's good.

from recogito-tei.