Hi, Trevor:
I don’t think that we’ve seen this particular issue, but we did have another
issue when upgrading from 1.5.x to 2.x which I’ll mention here in case it’s of
any use in your circumstance. For us, the issue was simply a plugin. In our
case, whenever we saved a record after upgrading,
Leilani,
Could you attach an example EAD file? I'm curious what happens when Unicode
characters are used in place of the character entities. I'm wondering if the
issue might simply be that the font used doesn't include italic characters for
the character entities that are tagged as italic (a
Hi Olivia,
Hear, hear!!! 😊
Just a quick note to say that this is something that we’ve discussed at Yale,
as well, and I think that we might start to address it via a plugin at some
point (it would be a nice feature to go directly into the core code, but in
order for that to happen, I’d think t
Lydia,
In the EAD files that you attached, both have invalid XML characters in them
(Unicode: 0x14). Those are easy to remove before re-importing in an XML editor
like oXygen, but I'm curious how they got into ASpace in the first place? In
any event, it's possible that that's what's blocking
Hi Lisa,
I’ve no clue what could be causing this, but others have reported the issue as
well. Hopefully the root cause of the issue can be identified with enough eyes
on the problem. So far, I haven’t seen this happen in Yale’s TEST PUI instance
(on 2.1.2) or on our DEV instance (on version 2
Annie,
The PUI still has a way to go with integrating digital objects, but the gist is
that right now to get the red Digital Record icon badge, you’ll need to use
that URI as a File URI subrecord, rather than (or in addition to) the Digital
Record identifier. Here’s a bit more info:
https://
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Wednesday, 01 November, 2017 3:38 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF
Stephen,
It looks like you’re using HTML elements there
Stephen,
It looks like you’re using HTML elements there (e.g. span and q), and although
the new PUI PDF process converts the ASpace JSON to HTML which is in turn
converted to PDF, I don’t think that it expects to find HTML tags. Given that
this process is converting to HTML anyway, though, I’d
could become part of the core code?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Monday, 16 October, 2017 3:07 PM
To: Archivesspace Users Group
Subject: Re
Hi, Joan.
In the PUI, yes, you can do this.
In the Staff Interface, you can also do this, but the approach isn’t as
obvious. But you can return every record that’s part of a specific resource by
searching for its URI fragment. For example, in http://test.archivesspace.org,
there’s a Reposito
Tara,
Just a wild guess, but since the EAD file seems to fail while trying to export
information about the Repository, can you edit your Repository record and make
sure that everything looks okay there? You can edit your Repository in the
staff interface by going to System --> Manage Repositor
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 --> EAD
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:
htt
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:
[7f48c48b-7c0a-4a31-9625-d88b32bb3
All,
I wish that I could offer technical advice on how to get things set up, but
unfortunately I'm of no use in this case. I do know that this feature used to
be configured on our Test Corpus site, though, and that it functioned as
expected at that time.
Here's what a message would look l
Megan,
I was just looking in the listserv archives,
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group, for
this, because I swear that someone else provided a fantastic answer to a
similar question a while ago. Anyhow, I can’t find it right now, so here’s my
stab at answe
Hi, Suzanne.
Yep, that's exactly the way to do it, and exactly why the "unassociated" option
was added.
Since top containers are scoped to repositories, though, if you have multiple
repositories in your installation, then you'll need to perform this action
within each repository. We've assi
Kari, all:
I’d also add that even though the ArchivesSpace note fields look like they can
support EAD markup (and proclaim to be “Mixed Content Enabled”), it’s not
really full-blown support like you’d get with an XML editor or a WYSIWYG
interface. For example, if I use the current tag-suggesti
Ben,
Barcodes are included in EAD exports, but locations are not included.
If you need to use EAD for requesting workflows, I’d probably suggest just
adding the top container URI to the EAD exports via a local plugin. That way,
you could get much more than the name of a location if you ever ne
Beth,
Just a guess, since I haven’t tested this out yet, but my hunch is that your
new value is missing in the Staff Interface because there’s no translation
value in the YML (Yet another Markup Language) file. The PUI is actually using
the database value for this particular element (though th
_group-boun...@lyralists.lyrasis.org
on behalf of Custer,
Mark
Sent: Wednesday, August 30, 2017 1:51:42 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF
Alice, all:
The new PUI PDF process does *not*
Alice, all:
The new PUI PDF process does *not* use EAD or the as-ead.html.xsl file.
Instead, it takes the data directly from ArchivesSpace, converts it to HTML,
and then converts that HTML to PDF. For the ASpace PUI workshop I created a
small plugin to illustrate how you can change the imag
Steve,
Thanks so much for including information about the Java libraries that this new
process that the PUI uses, as well as that link to that flying saucer user's
guide (it looks like that could be helpful in figuring out how much of CSS3,
etc., is supported for creating the PDFs!).
Mark
Alice, all:
The new PUI PDF process does *not* use EAD or any XSL that's still used on the
staff side. Instead, it takes the data directly from ArchivesSpace, converts
it to HTML, and then converts that HTML to PDF. For the ASpace PUI workshop I
created a small plugin to illustrate how you
Jesse,
Eventually, I’d love to have all of these options documented with examples on
this site:
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/66355303/Release+Phase
Right now, though, a lot of these common configuration options haven’t been
added there yet.
Here’s how to mak
Jesse,
Could you send me a copy of the EAD file?
On the "Container Inventory" page, there may or may not be facets depending on
the data. On the actual top-container page in the PUI (i.e. the second
screenshot), though, there should be listing of every archival object,
resource, and/or access
lse %>
-- Steve Majewski / UVA Alderman Library
From:
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
on behalf of Custer, Mark mailto:
Neal, Lance: thanks for diagnosing this issue!
The PUI search results should definitely still work in this case. We had
archival objects in our test corpus with missing titles, so I'm pretty sure
that this worked at some point, but it's definitely not working now, as you've
noticed. I think t
Wow. Yeah, it looks like this change wipes out unitids from the EAD export if
you migrated from the AT, like us, since ASpace stores those AT database values
as external IDs, and the exporter now won’t export the “internal” IDs if you
have any external ones:
https://github.com/archivesspace/ar
Kari,
This error happens when the EAD to PDF process is trying to create a link, but
there's no link to include in the PDF output.
The line number that's mentioned in the error is in the XSL-FO XML file, not
the EAD file (nor the as-eas-pdf.xsl file, which luckily isn't that big of a
file :)
...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Monday, August 07, 2017 11:44 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] PUI search results
Rachel,
>From your example that includes 5 searc
Rachel,
>From your example that includes 5 search results, I can say that the first 4
>results with the out-of-the-box PUI are intentional, since those first 4
>results occur within the Rockenback papers. That last search result for
>component 6, though, is not intentional! I'm afraid that we
Dan,
That feature should be configurable. At least, I know for sure that it was
configurable when this feature was in a plugin, but since our hosted is still
reporting linear feet, not inches (which I believe is the default, as you’ve
noted), I’m quite sure this option still exists (I just hav
_users_group-boun...@lyralists.lyrasis.org>
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Tuesday, July 11, 2017 12:44 PM
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "
Kate,
When linking a top container in this way, you just need to go to "Browse"
instead of Create. On the Browse list, just find the top container that you
want to link to from whatever context and then link to it (it's often easiest
to search for the other collection's finding aid title, for
Lydia,
Regarding your first question: One low barrier way to do this, I think, would
be to create a separate repository for everyone who would be doing basic data
entry tasks, like container listings. You could then make sure that they only
have editing rights to those container lists, and no
egards,
Zach
From:
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Wednesday, March 1, 2017 1:50 PM
To: Archivesspace Users Grou
Hi, Zach.
Just to check and make sure, could this be because you have unpublished
components?
Here's an example in the sandbox of what a resource record with a single
unpublished component will look like:
http://public.archivesspace.org/repositories/2/resources/7
That particular unpublished ch
Just a quick message to note that this has also been discussed for EAD3 and
will eventually be added to the schema:
https://github.com/SAA-SDT/EAD3/issues/506
So, it seems like a change request to ArchivesSpace would be pretty natural
once (and, better yet, even before) it’s available in DACS
Annie,
This probably isn’t very helpful, but so far I’ve only done this type of
sorting outside of ArchivesSpace (with regular EAD-to-EAD XSLT transformations,
which was helpful when I needed to ignore initial articles in the unit titles,
as well as converting an EAD file to an Excel file, sort
Dear Annie and Gregory,
You're correct that this is how the current PUI works.
The redesign is still under way, but it's due for its beta / candidate release
at the end of March, with a production-ready release planned for the end of
June. With the new PUI, any record that's linked to an Agent
Brian,
There's no mapping to import that data from an EAD file. I think your best bet
there would be to use the API to make those updates. I don't have any examples
of how to do that with top containers and locations, but maybe Bria, Noah, or
someone else out there has already done something
Yep, you can certainly do this, but just be careful, since the following two
containers will be imported as two different top containers (and there's no way
to merge top containers in the staff interface):
1
...
1
But as long as the barcodes are added to every instance of "box 1" in the EAD,
y
Suzanne,
Here's one workaround for that:
* Add a child-level component to the resource, and name it something
like "delete-me", and give it any level whatever (since those two fields are
required to create a new archival object).
* Select all of the archival components that yo
Dear Colleagues,
I'm writing to provide an updated timeline for the release of the new
ArchivesSpace Public User Interface. As many of you are aware, we have been
aiming to have a candidate release ready for December 16th, with the official,
production-ready release to follow in March 2017.
8
From:
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Tuesday
Kate, Dave:
Can you attach the EAD file? I wonder if this is being caused by an empty
container element in the source file, or something else related to a container
attribute?
Mark
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyral
Christine, Cheri:
I’ve been meaning to make a few changes to the XSL-FO Stylesheet that ASpace
uses to create PDFs, and it seems like this should feature request should be in
the core code. I doubt I’ll get around to this work until late December /
early January, but I’d be happy to submit a p
boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Friday, 11 November, 2016 9:48 AM
To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org)
Subject: [Archivesspace_Users_Group] Check out the test site of the
Dear ArchivesSpace colleagues:
I am writing to provide an update about the development of the new
ArchivesSpace Public Interface. As a reminder, here is the release timeline
that we drafted and shared earlier in the year:
* candidate release, 12/16/2016
* official testing per
h96Z0r-hkqodUzf7hdQ&s=740yfwjw57gZhC04Vk5w8GWaCFjTpYbv21AnaIKmWzg&e=>
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Wednesday, October 12, 2016 3:59 PM
To: Archivesspace U
Just a quick reply to say that we chose option 1, too, here at Yale. We tested
the migration process many times before we performed the official migration.
Maureen Callahan provided a window into the fun in the following blog post:
http://campuspress.yale.edu/yalearchivesspace/2015/04/23/read
Jane,
Is it possible that what you've noticed is related to this ticket?:
https://archivesspace.atlassian.net/browse/AR-1521
This bug affects editing of any note type, and it's particularly problematic.
I believe that we've just alerted staff not to use the "Delete" key because of
this when e
All,
The ArchivesSpace Public Interface Development group will be holding its next
conference call tonight, Tuesday, September 20th, 6 p.m. EDT.
Anyone with an interest in contributing to the development of the new
ArchivesSpace Public Interface is welcome to join the call to listen in,
althou
Kari,
That text is added to the profiledesc section of the EAD file by ArchivesSpace
whenever the EAD output is created. If you want to edit how that appears (or
if it appears at all), one option is to edit the XSL transformation. Here's
where the profiledesc is called in the transformation
All,
The ArchivesSpace Public Interface Development group will be holding its next
conference call tonight, Tuesday, September 6th, 6 p.m. EDT.
Anyone with an interest in contributing to the development of the new
ArchivesSpace Public Interface is welcome to join the call to listen in,
althoug
oup-boun...@lyralists.lyrasis.org>
[mailto:archivesspace_users_group-boun...@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 Interf
EwQd5RW52bC9xguJuB5p6a8gH8m40Xi-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
mailto:mark.cus...@yale.edu>> wrote:
Kari,
Alth
Dear Jesse,
With the current public interface, I believe that this would be something that
you'd need to modify on your end.
With the new public interface, which is scheduled for release next year (with a
candidate release this December), the search results are going to include more
informatio
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
All,
I haven’t had a chance to test this yet, but just a thought: is it possible
that your user account doesn’t have permissions to create/update new top
containers? Surely the option shouldn’t display if you don’t have those
permissions, but perhaps it always displays. In any event, I’d giv
All,
The ArchivesSpace Public Interface Development group will be holding its next
conference call tonight, Tuesday, August 23rd, 6 p.m. EDT.
Anyone with an interest in contributing to the development of the new
ArchivesSpace Public Interface is welcome to join the call to listen in,
although
All,
The ArchivesSpace Public Interface Development group will be holding its next
conference call tonight, Tuesday, August 9th, 6 p.m. EDT.
Anyone with an interest in contributing to the development of the new
ArchivesSpace Public Interface is welcome to join the call to listen in,
although w
101 - 163 of 163 matches
Mail list logo
