• If a core is uploaded its entries are not syntax highlighted in the "Full Core" tab,
• if a new entry is added with the coreBuilder the uploaded one will get syntaxhighlighting, but not the new one
• it will get highlighted though when another entry is being deleted
• Alternatively if a core is uploaded and new entries are being added the last entry will not be syntax highlighted

There is definitely some inconsistency here that needs further testing

If an app grows longish the control entries for "Add", "Group", and "Cancel" might be outside the browser viewport.

Moreover as coreEntry doesn't allow scrolling one can not check the whole entry.

creating an entry with rdggrp elements and adding it to the full core strips the rdggrp elements and instead adds a flat app(rdg+) into the full core

N.B. uploading a core with rdggrp works perfectly fine

when creating an entry and not adding it to the full core but instead hitting "cancel" the created groups and their association to the sources will not be resetted;
either this should be done by default or a global "reset/clear groups" button should be available

Dear Raffaele Viglianti,
I am currently looking at solutions allowing me to practice different semantic annotations on theatrical texts from the French 17th and 18th centuries, and I was wondering to what extent I could use coreBuilder for this.

To explain my needs, I'll start with a span of text, as it is actually encoded in XML/TEI:

Currently it doesn't seem possible to group empty pointers

Allow the user to undock and drag the current entry panel.

It needs to reset after an entry has been added.

rdggrp misses the tie typical camelScript. Although the namespace is not outputted the TEI-ishness is obvious to the informed reader and should conform to TEI tag-names

E.g. to support use cases like building a listRelation with non-mutual relationships, where a relation element can have both @active and @passive pointers.

See http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSREL

if selected elements get added to a group they are no longer available under the respective ace editor of the source, ergo they cannot be deleted from the app

alternatively a "remove form group" mechanism would be feasible or reflecting the grouping under the ace editor

Custom attribute values can be somewhat parametrized by the user (e.g. with %filename). It would be useful to allow some basic XPath (e.g. //TEI/@xml:id) for something like wit="#TEIid".

Only XPath 1 can reasonably be implemented in JavaScript, however.

currently it is not possible to generate multiple rdgGrp elements in the app entry; but already in one of the first attempts with coreBuilder this seemed necessary

Donloading a core file from the core builder works but the xml file does not have the generated core entries as content but only:
<core>[object Object]</core>

browser: firefox

values are the filenames and id of parent div

is this due to missing xml:id in our TEI files or default?
Using xml:id (which we will add ASAP) seems more feasible
div xml:id doesn't seem necessary here

Submitter: Anonymous
This is a test for public bug report

Uploading a preexisting core, then adding a new entry raises some other problems (beisdes #8):

• when downloading the core it will only contain the newly created app:s not the preexisting one- the preexisting entry will only result in a sting "undefined" as first child of