ewg118 / eaditor

EADitor is an XForms framework for the creation and editing of Encoded Archival Description (EAD) finding aids using Orbeon, an enterprise-level XForms Java application, which runs in Apache Tomcat.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Annotating problems

Hillarchives opened this issue · comments

For example, tried several times, saving each time, to add annotations to page nnan187919_0004 at http://admin.numismatics.org:8080/orbeon/eaditor/admin/edit/tei/?id=nnan187919 , but annotations would disappear. Also, it wasn't parsing Donum links on page, though parsing was successful on other pages.

Went back and was mostly successful with page, except parsing of "Sims sale" donum note at bottom.

What is the Donum URI that you're using?

On Mon, Aug 4, 2014 at 2:48 PM, Hillarchives notifications@github.com
wrote:

Went back and was mostly successful with page, except parsing of "Sims
sale" donum note at bottom.


Reply to this email directly or view it on GitHub
#20 (comment).

http://numismatics.org/library/16117

What is the Donum URI that you're using?

On Mon, Aug 4, 2014 at 2:48 PM, Hillarchives notifications@github.com
wrote:

Went back and was mostly successful with page, except parsing of "Sims
sale" donum note at bottom.


Reply to this email directly or view it on GitHub
#20 (comment).


Reply to this email directly or view it on GitHub:
#20 (comment)

It appears that Donum does not export XML containing ampersands correctly,
so it's impossible to parse this particular record (with Sotheby, Wilkinson
& Hodge 60). The record will either have to be updated to replace & with
'and' or someone will have to fix Donum's code.

On Mon, Aug 4, 2014 at 3:14 PM, Hillarchives notifications@github.com
wrote:

http://numismatics.org/library/16117

What is the Donum URI that you're using?

On Mon, Aug 4, 2014 at 2:48 PM, Hillarchives notifications@github.com
wrote:

Went back and was mostly successful with page, except parsing of "Sims
sale" donum note at bottom.


Reply to this email directly or view it on GitHub
#20 (comment).


Reply to this email directly or view it on GitHub:
#20 (comment)


Reply to this email directly or view it on GitHub
#20 (comment).