Re: [Archivesspace_Users_Group] Top container record corrupted

HI, Christine: Sorry, I should have put that in my original email. We are using v. 2.1.1. Thanks. George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 From:

Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

All, We have identified the issue with the requesting material email and have put a fix into the core code in GitHub: https://github.com/archivesspace/archivesspace/pull/971. So, it will be in the next release, that we are expecting to come out soon. Best, Laney Laney McGlohon ArchivesSpace

Re: [Archivesspace_Users_Group] [EXT] Re: 2.1.2 re-indexing loop

Hi Jeremy, I'm definitely going to put a support ticket in for you then. The tech folks can help troubleshoot what's going on overall. You'll see another message about that from me directly in a minute. (And it'd be great if you'd post back to the list when it's resolved.) Christine

Re: [Archivesspace_Users_Group] AS PUI Terms for Database Mapping

Hey Suzanne, The reports team has been working on creating a data dictionary for the ArchivesSpace database. I think adding the corresponding PUI terms would be a great enhancement to the data dictionary. Carolyn Runyon is the head of the reports team, so you might want to touch base with

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

Hi Jeremy, It looks like you’ve gotten a lot of help here on the list, but if you’d like to move this over to a tech support ticket at some point, please let us know at archivesspaceh...@lyrasis.org. Either way, I’m sure those on the list will be eager to

Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

Yes, Trevor that would be great! Mark, I’ll look into whether we can try tweaking that xml_cleaner.rb file. That scenario you describe below is exactly what’s happening for us—although I should mention that we can still export valid EAD. For the AT example (which is in a Separated Materials

[Archivesspace_Users_Group] AS PUI Terms for Database Mapping

Does anyone have a reference for the PUI screen terms matched to Database mapping? Will you share? This would help users who don't have access to the backend better understand the system. Does anyone have interest in formalizing this for other users? Suzanne Suzanne Stasiulatis | Archivist II

Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

Trevor, That would be fantastic! Benn, For your PDF error, I think that might be caused by a slightly different issue. The new PUI “Print to PDF” process converts that ArchivesSpace JSON record to HTML and then converts that HTML into a PDF file. So, it doesn’t use the same JSON -->

Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

The logic for converting ampersands in the EAD exporter is to only convert them if they are immediately followed by a space, otherwise they are assumed to be an entity. This is part of the process of sanitizing mixed content, which is actually applied to most fields. However, the ampersand

Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

Dave, Benn: Another important point here is that the ASpace staff interface attempts to handle both “ & “ and “ “. Those spaces are (quite unfortunately) important here. is a special HTML and XML entity reference for the ampersand character. A nice, short overview is provided here:

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

Does this error happen in the PUI view? Based on this error: INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2:

Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

Hi Benn, This is a recurring issue I hit over both Harvard and Smith’s collections – it’s a consequence of ASpace not really having a distinction between mixed content and plaintext content. Unfortunately, there isn’t really a good solution. The best solution as far as I’ve been able to