[Archivesspace_Users_Group] Missing text from between HMTL tags in Public Interface

Thu Sep 1 10:02:25 EDT 2016

Thanks again, Mark.  HTML table elements would be great, but <ul> or <ol>
wouldn't be a good work around in our case, because we really want the
information to be in multiple columns. Otherwise it will end up many many
screens long.

/ Lara Friedman-Shedlov

On Thu, Sep 1, 2016 at 8:55 AM, Brian Thomas <bthomas at tsl.texas.gov> wrote:

> I have been working on a crosswalk for our ead, we are still in the
> beginning phases, and my recommendation was to take items out of the
> item/row and make them a <ul><li> or <ol><li>. Should we not be, then
> waiting for the improvement? We don’t have many tables, but we do quite a
> large number of <item><row> lists.
>
>
>
> Thanks,
>
>
>
> Brian Thomas
>
> Electronic Records Specialist
>
> Texas State Library and Archives Commission
>
> 1201 Brazos Street
>
> Austin, TX 78701
>
> PH: (512) 475-3374
>
> e-mail: bthomas at tsl.texas.gov
>
> tsl.texas.gov
>
> [image: cid:image001.jpg at 01D029A2.37194C70]
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Custer,
> Mark
> *Sent:* Thursday, September 01, 2016 8:16 AM
>
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Missing text from between HMTL
> tags in Public Interface
>
>
>
> Hi, Lara.
>
>
>
> Depending on how you look at things, the EAD table elements could be
> considered a different type of issue, particularly because ArchivesSpace
> doesn’t fully support those elements right now since you can’t add them
> directly in the staff interface.  My strong preference, though, is to
> ensure that these elements can still be rendered as HTML table elements in
> the new public interface.  So, that is on the “to-do” list, and I hope that
> it’ll be available with the candidate release of the new public interface,
> but since the staff side still doesn’t support encoding tabular structures,
> it’s possible that this might slip until it’s determined whether or not the
> staff interface will support working with tabular structures (i.e. creating
> and editing tables in the staff interface, not just being able to import
> the table elements into a note field).
>
>
>
> All that said, I’ll make sure that there’s at least one table in our “test
> corpus” (if there isn’t already) so that the issue will be apparent to our
> testers.  Additionally, I added an umbrella ticket for a few
> metadata/display issues earlier in the year, which you can find here:
> https://archivesspace.atlassian.net/browse/AR-1485  Once this ticket is
> addressed, we’ll actually break them out into individual tickets (although
> I hope that fourth bullet point, which is about transforming EAD into
> corresponding HTML elements, will become a single ticket… especially since
> some of those elements are already being handled correctly in the new PUI).
>
>
>
> Mark
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Lara
> Friedman-Shedlov
> *Sent:* Wednesday, 31 August, 2016 5:27 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Missing text from between HMTL
> tags in Public Interface
>
>
>
> Thanks, Mark.  We've been experiencing this same problem as Kari.
>
>
>
> A similar issue we've noticed is that ASpace seems to ignore EAD <table>
> elements (and their children like <tgroup>, <tbody>, <row> and <entry>) in
> notes like Biographical / Historical.  In this case the text does show up
> in the public interface, but it is unformatted.  See for example
> http://archives.lib.umn.edu/repositories/7/resources/959
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__archives.lib.umn.edu_repositories_7_resources_959&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=tta6rwzzrKJBMqqG2gkmblkcnlZJk1X7cGWe5DgadNU&s=0D6pwwS9TAUsXQkxWwa2JZiajQ-1CzsqGM771-DoDcY&e=>
>  -- look at the last paragraph in the historical sketch.  It should appear
> in 3 columns (see http://special.lib.umn.edu/findaid/html/ymca/
> yusa0009x2x40.phtml
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__special.lib.umn.edu_findaid_html_ymca_yusa0009x2x40.phtml&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=tta6rwzzrKJBMqqG2gkmblkcnlZJk1X7cGWe5DgadNU&s=f-yZEwQd5RW52bC9xguJuB5p6a8gH8m40Xi-iylWf5k&e=>),
> but instead it's a solid block of unformatted text.
>
>
>
> Is this also on the radar or is this a separate issue?
>
>
>
> / Lara Friedman-Shedlov
>
>
>
>
>
> On Wed, Aug 31, 2016 at 3:54 PM, Custer, Mark <mark.custer at yale.edu>
> wrote:
>
> Kari,
>
>
>
> Although I know that this doesn’t help right now, I can assure you that
> this sort of behavior has been fixed in the new public interface, which is
> due out next year (this year if you count the candidate release that’s
> scheduled to come out in early December)…  assuming that you’re talking
> about EAD elements and not HTML elements.
>
>
>
> For instance, the following is HTML with mixed-content:
>
>
>
> <ruby>
>
>   明日 <rp>(</rp><rt>Ashita</rt><rp>)</rp>
>
> </ruby>
>
>
>
> ASpace won’t know what to do with that (and it shouldn’t be in an EAD
> finding aid, at least not with the current EAD specification), but if it
> were in ASpace then I’d argue that the best thing that could happen would
> be for all of the text to display to the public minus those three elements.
>
>
>
> I can’t see the pictures that you added to the email (see the postscript
> below), but I assume that you are talking about mixed-content of EAD
> elements since you mention the <title> tag, like so:
>
>
>
> This is text from a unittitle, and it has a <title>Title</title> and a
> <corpname>Corpname</corpname> in it.
>
>
>
> (HTML also has a title element, but it only occurs in the HTML head
> element, which is rendered as the page name, search result title, and stuff
> like that…  i.e. not stuff in the body of the page)
>
>
>
> And if that’s the case, the new public interface will display it as
> expected without any of the EAD tags visible.
>
>
>
> Mark
>
>
>
> p.s. the pictures didn’t seem to come through in my email, but I’m well
> aware of how mixed-content is handled on both the staff and public side of
> ASpace, so I think that I can still “see” exactly what you’re talking about
> J
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Kari
> R Smith
> *Sent:* Wednesday, 31 August, 2016 3:14 PM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] Missing text from between HMTL
> tags in Public Interface
>
>
>
> Hello all,
>
> have you seen this behavior and have suggestions on how to fix it?
> Because there are 4 different ways the data is being rendered in different
> parts of the interface (staff and public) we are curious as to how to
> proceed. The behavior in the Public view is the most worrisome because the
> text disappears altogether.
>
> Thank you for suggestions.
>
>
> Issues with Components
>
> 1.   When viewing a component with a <title> tag in it to modify the
> display, the tag appears as part of the title text. This title displays the
> same in both the public and staff view. See below:
>
>
> [image: Picture 1]
> [image: Picture 5]
>
>
>
> *It does not appear as part of the title in the component list from the
> staff view: *[image: Picture 2]
>
>
>
> *From the public view of the component list, text between these tags
> disappears entirely*
>
> [image: Picture 4]
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=tta6rwzzrKJBMqqG2gkmblkcnlZJk1X7cGWe5DgadNU&s=kjrVlAeRaO5CDFPdTnHRD_UnFM0C3H7ICozL3VILfBs&e=>
>
>
>
>
>
> --
>
> _________________________________
>
>
>
> Lara D. Friedman-Shedlov
> Kautz Family YMCA Archives | University of Minnesota Libraries
> ldfs at umn.edu |  612.626.7972 | www.lib.umn.edu/ymca
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lib.umn.edu_ymca&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=tta6rwzzrKJBMqqG2gkmblkcnlZJk1X7cGWe5DgadNU&s=UhWa_Zf4wgkRNRnWsL8hzAz2VlRrAH-cvgYw_2U667Y&e=>
> | @yarchives
> __________________________________
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>

-- 
_________________________________

Lara D. Friedman-Shedlov
Kautz Family YMCA Archives | University of Minnesota Libraries
ldfs at umn.edu |  612.626.7972 | www.lib.umn.edu/ymca | @yarchives
__________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160901/e5670ff9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160901/e5670ff9/attachment.png>