[Archivesspace_Users_Group] note contents/ead export

[Custer, Mark]

Ben,

I haven’t tested this thoroughly, but my understanding is that the exporter in the aspace-110-plugin (and maybe the core code, too) will now apply <p> tags wherever it encounters singe line breaks in a notes field, which is a bit different than how the AT used a double line break for the same purpose.  That said, neither system will change a single line break to an EAD <lb/> element, so those will need to be hand-encoded.

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman
Sent: Thursday, December 04, 2014 9:42 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] note contents/ead export

Steve, great news, thanks!

Do we know whether 1.1 still applies the <p> tags in notes in the same manner on EAD export?

-Ben


________________________________
From: "Steven Majewski" <sdm7g at virginia.edu<mailto:sdm7g at virginia.edu>>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Sent: Wednesday, December 3, 2014 5:23:10 PM
Subject: Re: [Archivesspace_Users_Group] note contents/ead export


Ben:
 I believe this is fixed in 1.1.0 + aspace-110-plugin. ( or if you build from github master )
 It is fixed on export in the serializer, which means that if you upgrade ArchivesSpace and keep existing data
 they will export without CDATA escaping.

— Steve Majewski



On Dec 3, 2014, at 5:08 PM, Ben Goldman <bmg17 at psu.edu<mailto:bmg17 at psu.edu>> wrote:

Hello,

I apologize if this has been addressed elsewhere, but I couldn't find an answer after searching in the Google Group or Pivotal Tracker (side note: is there an easy way to search this listserv's archives?).

I've noticed that the block text found in the Content fields of Notes, when exported as EAD, is wrapping that text in this:

<![CDATA[   Text. text. text.  ]]>

Any idea why this is or what we can do to adjust it?

On a related topic, a lot of our Bio/Hist and Scope/Content are multi-paragraph notes that had <p> tags embedded appropriately in AT, but we apparently lost these tags/embedded content for our notes in the migration to ASpace. ASpace applies bookend <p> tags around the entirety of the note on EAD export, but this results in code like this:

<p>Paragraph.

New paragraph.

Last paragraph.</p>

We're currently preparing to republish all our finding aids using the ASpace API, but would love to fix this first. Does anyone have ideas on how we might remediate this without manually checking/editing every resource? We're still running 1.09, so if someone tells me the answer is an upgrade to 1.1, I will be thrilled!

Thanks,
Ben



Ben Goldman
Digital Records Archivist
Penn State University Libraries
University Park, PA
814-863-8333
http://www.libraries.psu.edu/psul/speccolls.html
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141204/aaadd25f/attachment.html>