For internal linking in EAD, you can use the "@target" attribute. There is a
feature in the PUI that exploits this, as well. The documentation is a bit
rough, but here's a link:
Liz,
We are starting to work on this as part of the specification for
https://archivesspace.atlassian.net/browse/ANW-1209 (thanks again to Cory for
doing this work!), which focuses on adding digital object thumbnails in a
standardized way to both the staff and public interface of ASpace.
As
Benn,
Yes, this is a great feature request!
It was discussed as part of the PUI enhancement phase for 2.1, but never got
added due to the additional work required (e.g., month names would also need to
be added to the YML files for translation purposes). It was also hoped that
there might
Lev,
Accession records can be published or unpublished in the staff interface, and
if the accession records are unpublished, then those records should not show up
in the ArchivesSpace PUI. If I recall correctly, though, there was a bug in the
initial release of the PUI in ASpace 2.1 that
Ed,
Not exactly. It's not a problem of any HTML encodings in the URL (e.g. %3A for
a colon), which should be fine.
However, if you go into edit those digital objects in the ASpace staff
interface and open the File URI section, you should see something like:
It looks like Steve’s diagnosis below is spot on. Those links have HTML in
them, but you just want the links, so that’s why things aren’t working.
Ed, if you have access to run SQL queries against your ArchivesSpace database,
I’d start there. Just look for HTML tags in your file version URIs
Tom,
Not sure if it will help (and not sure if you shared your config.rb file in a
previous message), but have you tried:
* turning off the Solr backups during the re-indexing
Hi Bridger,
Just a very quick reply, as I haven't had time to look at the newest release of
ArchiveSpace, but...
1. Yes, I think you'd need to use a plugin or other mechanism to do this
(lots of plugin examples out there, but if you have any questions about that,
there are lots of people
___
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Custer,
Mark
Sent: Friday, November 17, 2017 3:35 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace
Hi Olivia,
Hear, h
Karen,
In addition to Michelle's great advice, if you're adding notes, you'll want to
follow the same model of creating the whole note and posting it.
Here's an ugly mocked-up example:
new_sc_note_content = "Whatever note you're adding"
note =
David,
In addition to what Zach and Andrew mentioned, I would also set
"pui_indexer_enabled" to false in this case.
Also, all the configuration defaults are here:
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb.
I always have to look at that to
Hi, Lev.
Short answer: you can select “otherlevel” and then type in “sub-subseries”
(even “sub-sub-subseries” and whatever else that’s needed). You might need to
update your display code, but that approach would keep the EAD valid. I'm
attaching a screenshot for how to do that in
Dear Amanda,
There's no way to do this in the staff interface.
This could be accomplished with a plugin, however. Alternatively, you could
add a transformation step after extracting the EAD file from ArchivesSpace. At
Yale, we rely on both approaches. I will usually only take the plugin
hivesspace_users_group-boun...@lyralists.lyrasis.org>
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
On Behalf Of Custer, Mark
Sent: Wednesday, September 30, 2020 3:12 AM
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archives
like what I need. I’ll try it out and let you know.
Thanks again!
Bennett
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 Custe
Bennet,
Not spammed out, so no worries!
In case it helps, a couple years ago I was able to get a hokey script set up
(with help from others – thanks again, Dallas and Dave!) to download MARCXML
files from OCLC and post those to ArchivesSpace using that endpoint. Here’s a
snippet that shows
Linda, all:
I'd also say that a new report could/should be created that doesn't rely on
event records in this case. Adding reports to ASpace is much easier now than it
used to be, and I think that having one that relied on the "Processing Status"
field in this case would make a lot of sense.
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] PDF export issue
Yes, a sample would be useful to try to reproduce the issue. It would also be
interesting to know if both the staff PDF export and the PUI PDF show the same
problems. ― Steve M.
On Sep 29, 2
I'm curious if this has always been the case, as well, but it would seem like
it has been. I knew that the repository and location endpoints could be
accessed but didn't try any of the rest for some inexplicable reason. Not good
to have agent contact details available that way.
Given which
Dear Hitomi Matsuyama,
Which version of ArchivesSpace are you using?
I'm not familiar with those configuratio settings, but I suspect that they
might just be for the PDF formats of the Reports, not for the PDF format of the
EAD conversion process.
On newer releases of ArchivesSpace, the
Betts,
Exactly what Karen and Dan said!
I would caution you not to rely exclusively on the staff interface to do this
work when working in a multi-repository ASpace installation, though. When we
did a similar project, we exported all of the data to external spreadsheets to
make the
Natalie,
When we set our system up, I was hoping that we would use Google Tag Manager
(GTM) to do exactly that, but I don't think that we have configured things for
that yet (and I've never used Google Tag Manager, so I'm just assuming that it
would be feasible to do so ).
Given how ASpace
Kevin,
What you've done for now sounds like the best option within the current
structure of ArchivesSpace.
Although ArchivesSpace could be updated with other controlled lists, like
ISO-639-3, I'd be curious if it would be possible -- and, more importantly,
useful -- to try to adopt the IETF
on, but it's working for now, which is the important part. Thanks for the help
tracking that down.
Best,
Chris
On Tue, Aug 18, 2020 at 6:12 PM Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
Chris, Lora:
Okay, so I just did a bit more digging (but not enough yet), and I'd say that
there must
ly important for us to be able to output PDFs directly from the
application.
Best,
Chris
On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
Chris,
No clue if it's related or not, but it looks like a gem that's utilized for
XSLT transformations in ASpace w
Chris,
No clue if it's related or not, but it looks like a gem that's utilized for
XSLT transformations in ASpace was switched out recently (saxon-xslt ->
saxon-rb). I wonder if the new gem (and/or new version of saxon) is more
strict, and only now throwing an error because of that?
In any
Bridger,
Regarding the first issue, are those two resources "suppressed" by any chance?
A suppressed record cannot be seen in the staff interface by most users unless
they also have the ability to view suppressed records. Since you mentioned
that you could see it as an admin user, that's my
Wendy,
I'll let others weigh in about 2.8, but I expect it should be released soon.
That said, if you are planning on using the AT to ASpace migration tool (i.e.
https://github.com/archivesspace/at-migration), then it looks like you would
need to start off with ArchivesSpace 2.6. Once the
Lisa,
The snippet you provided below looks fine. Can you attach an example EAD file?
Given the error about the "indicator" missing, though, it's possible that the
file has an empty container tag in the EAD (e.g. ). If so, that would likely cause an error since every
top container requires a
Eddie,
ArchivesSpace requires a few different data elements to be present before a new
Resource record can be saved. Based on this error, it looks like the MARC
record does not have any date information where the ArchiveSpace MARCXML
importer would expect dates to be present (i.e. dates : At
title from a movie
reviewer's collection.)
Kevin
On Tue, May 19, 2020 at 4:08 PM Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
Kevin,
I love that approach! Much cleaner to write those queries against the EAD/EAC
exports than having to do all of the table joins directly on the datab
records (or at least the URLs to any
associated resource records, so we could easily find the relevant bio/hist
notes). Our instance of ArchivesSpace is hosted by Lyrasis so we contacted
them to ask about it and were told this is "not possible." I found that
surprising and wonder if
All,
Is anyone else working on Agent-related cleanup projects in ArchivesSpace right
now? We’ve got a couple of those going on at Yale, and I wanted to mention one
of them on this listserv since I said that I would last night on Twitter . My
reasoning was that it would be better to share
Hi, John!
Short answer: yes. But you have to use @id attributes on the containers,
otherwise I think that the ASpace importer will assume that the containers are
nested (details are defined here for the importer logic,
2905
cdibella13 (Skype)
[ASpaceOrgHomeMedium]
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Custer,
Mark
Sent: Friday, April 24, 2020 9:05 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Request for Assistance with
Troubleshooting
James,
I haven't had a chance to look into this, but my hunch is that the issue would
reside in ArchivesSpace's EAC exporter, not your database. The EAC importer and
exporter in ArchivesSpace aren't really finished; you can never (for instance)
export a valid EAC record, regardless of the
Henry,
The server logs will give you one perspective, but another perspective that you
can possibly get from a page-tagging approach like Google Analytics would be
all of the other stuff that you an configure (e.g. the ability to add tags with
Google Tag Manager), which I only bring up since
Henry, all:
We did exactly what Joshua mentioned... added the snippet as provided by Google
Tag Manager to the layout_head.html.erb file, and that's it.
Just out of curiosity, is anyone using alternatives to Google Analytics, such
as https://matomo.org, with their ASpace PUI?
Mark
Jordon,
1. As far as I know, you would have to do that in a plugin right now. Here's
an example, since it's not obvious where one would do that:
Hi all,
Sorry for the extra message. I need to not use Outlook online. I didn't mean
to send that message to the whole list. Sorry about that
Mark
From: Custer, Mark
Sent: Wednesday, February 26, 2020 9:22 AM
To: Carbone, Maura ; Archivesspace Users
Maura,
No problems at all sharing any and all Resource and Archival Object JSON
records. The only things that would have confidential info at the Beinecke are
Accession JSON records.
It looks like the 3 files in "ycal_mss_42" are identical, though (all for the
Resource record, though the
Cory,
I just tested this out with a new build of ASpace, since I knew this worked
before! At first I didn't get it to work either, but that was because I just
copied over one of your examples as is. When I looked at the ASpace JSON
records, though, I realized that your genreform example just
PM
To: Custer, Mark
Cc: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error Generating PDF
Ha! I didn’t even know that was valid EAD! — Steve.
On Jan 16, 2020, at 3:48 PM, Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
Justin,
I just took a quick look, and it a
Justin,
I just took a quick look, and it appears that the issue is due to a nested
bioghist note, which ArchivesSpace doesn't support. That nested note is also
followed by two more bioghist notes, which look to be complete duplicates of
the nested bioghist note. So, short answer: delete
info? Just curious!
Lydia
From:
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
on behalf of "Custer, Mark" mailto:mark.cus...@yale.edu>>
Reply-To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Tuesday
Room B22
tel:213-740-8180
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, January 7, 2020 11:13 AM
Bo,
This sounds like a very tricky / fun project!
Though I have not gone through the exact same scenario, I have gone through a
process of matching containers in finding aids with item records in
corresponding MARC records in an ILS. As with most problems of this type, I
suspect that you
du<mailto:gcodding...@mcdaniel.edu>
(410) 857-2793
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: Monday, December 16, 20
Gwen,
Which version of ArchivesSpace are you on?
Here’s an example of an agent record in the PUI that uses both the Dates of
Existence subrecord (for specific birth and death dates) aas the date field in
the Names subrecord: https://archives.yale.edu/agents/people/81438
Also, have you tried
Corey,
First of all, welcome to the ArchivesSpace community! Your project will
definitely make you an ArchivesSpace expert in no time.
Glancing at your workflow document, it looks like you’ve got all of your bases
covered. I would strongly suggest running the AT to ASpace migration a couple
ASpaceContainerManagement, which
provides a great introduction, along with videos!
Mark
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Friday, 22 November, 2019 1
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: Friday, November 22, 2019 9:34 AM
To: Archivesspace
Jennifer,
If you can share a sample EAD file that isn't uploading, someone might be able
to pinpoint the issue that way if the error is in fact due to the file itself.
Additionally, have you tried uploading the file to
http://test.archivesspace.org/staff/? If you can upload it successfully
Julie,
Not sure if this is what you're asking about or not, but the following SQL
query would return all of the repository IDs along with their corresponding
corporate agent IDs:
SELECT
r.id AS 'repository id',
r.agent_representation_id as 'agent id',
r.repo_code,
r.name,
the additional pointers. (And sorry for
high-jacking your thread, Steve!)
On Fri, Nov 8, 2019 at 8:20 AM Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
Seth,
Here’s another example:
search?type[]=archival_object=1=
{
"query": {
"op":
Seth,
Here’s another example:
search?type[]=archival_object=1=
{
"query": {
"op": "AND",
"subqueries": [
{
"field": "keyword",
"value": "39002102378974",
"jsonmodel_type": "field_query",
"negated":
:
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, August 13, 2019 8:51 AM
To: Archivesspace
Hi Ed,
Those external IDs were added to the core code of the ArchivesSpace EAD
exporter at some point, which can result in some surprises (see the references
to "external_id" here
https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L139-L162
).
Benn,
Alex is exactly right.
At Yale, we use the length configuration to help ensure a basic level of
validity (one of our repositories has 9 character barcodes, and the rest have
14 character barcodes). I can also add that during the development of the top
container module, I was hopeful
Dear Freya,
Unfortunately that's right. The rights statement records (as well as some
other record types, like event records) do not appear in the public interface
as far as I'm aware. They also do not get added to EAD exports (although they
could, if there were a mapping for that data).
Patrick,
Just taking a quick look at this, I wonder if the issue might have something to
do with the relationship between the repository record and its corresponding
corporate agent record? Do both of those records (the repository record and
the corporate agent record associated with the repo
Lydia,
ArchivesSpace has a variety of "uneditable" controlled value lists that not
even administrators can edit in the application (the ability to suppress unused
values from uneditable lists was added after the initial release of
ArchivesSpace, which is a great feature, but that won't help
Danielle,
I’ve had to do something similar recently, so I’ve pared down the query that I
used to just grab a few bits of data in the Resource table and then combine
that with any extent information associated with those Resource records. The
output is one row per Resource. If the Resource
Chelsee,
In case you don't have immediate access to the server to force a full re-index,
check out the Background Job pages (or Import Job pages, depending on which
version of ASpace you're using). Even though the job can have a status of
"Completed," it's possible that no records were
Happy New Year, and happy Wednesday:
I wanted to follow up on this blog post,
https://archivesspace.org/archives/2534, now that Yale is using the
ArchivesSpace Public Interface in production.
Every once in a while, I run a few online searches to see who else is using the
public interface.
Julie,
It looks to me like this works as expected in a vanilla instance of the ASpace
PUI. See http://test.archivesspace.org/repositories/2/resources/45 (complete
aside: it's great that LYRASIS keeps this test site up, especially for testing
purposes!). I just mocked up an example, and here
John,
Exactly what Steve said!
As an aside, one thing that I thought about (quite a while back now, I guess it
was) was adding those mappings to the JSON-LD metadata that are currently only
applied on Resource, Repository, and Agent pages within the PUI (if you view
the source of a Resource
record, but that one record is giving
> me the same error message as the full sheet.
>
>
> Caitlin
>
>
>
> On Thu, Dec 20, 2018 at 2:09 PM Custer, Mark wrote:
>
> Caitlin,
>
>
>
> It looks like that error means that the conversion process is try
Caitlin,
It looks like that error means that the conversion process is trying to replace
some text (using “sub”), but there’s no text there at the point that it’s
trying to do the replacement (hence the “nil” part). Hard to say exactly what
would be causing that without seeing the CSV file,
Miloche,
That is some first-rate documentation! Thank you. I almost always forget how to
select multiple adjacent records since I so rarely do that (and switching
between CTRL and Shift is not so intuitive, and I always try to start with the
Shift key).
I’m going to print out your email and
...@lyralists.lyrasis.org
on behalf of Custer,
Mark
Sent: Tuesday, November 27, 2018 9:23:13 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Bibliography note not displaying in PUI
Stephen,
This looks like a bug to me. I haven't had much time
Stephen,
This looks like a bug to me. I haven't had much time to look into it, but I
have managed to replicate the issue and it appears to affect both the PUI *and*
the EAD exports, as you note. The second part is very strange, since I know
that I've tested those notes via EAD exports a few
al Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Custer,
Mark
Sent: Monday, November 26, 2018 3:42 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing
Zach,
No, sorry. That bit of SQL was run against the
that SQL
block? I do not see a way to edit the XML from within AS itself, so I'm
thinking that leaves the mysql DB or through the API.
Regards,
Zach
-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Custer,
Mark
Sent: Monday, November 26, 2018 2
DHXMsIicCSA%3Dreserved=0
It would be great if you could include in the tags “ATMigrator.” Thanks!
Lydia
-on behalf of Dev. Pri.
From: on behalf of
"Custer, Mark"
Reply-To: Archivesspace Users Group
Date: Monday, November 26, 2018 at 12:36 PM
To: Archivesspace Users Group
Subject: R
Zach,
I'd suggest exporting the EAD file and taking a look at the file that way (and
I'd be happy to take a look if you can send it to me).
Those "ns2" namespace prefixes are likely from Archivist's Toolkit, which at
some point started appending that prefix for the xlink namespace (which is
Adrien, Susan, Vernica, and all:
Add me to the interested list! We are not using Alma right now, but since we
will eventually migrate from our current ILS to another one that has a robust
API, I’d love to keep up with what other institutions are doing.
I’ll also say that my thoughts on the
David,
This is the result of some new inheritance features that have been added to the
public interface (and its index). Here's a bit more info:
Nancy,
Just a quick note to say, primarily, HEAR, HEAR!!!
Now, as for tips, I’d also suggest that “shared terms” just cannot be reviewed
in the staff interface at this time, even if you switch repositories like a pro
with multiple browsers. The reason: what you see in the “Linked Records”
Hi, Aditi.
So, I don’t know how best to approach this, but I can say how we’ve approached
this at Yale for the time being. We’ve updated our solr/schema.xml file to use
the Krovetz stemmer, which is a non-aggressive stemmer that works well for the
English language since it’s primarily
Kevin,
In addition to what Nancy and Steve have already mentioned, I'll add a few
other things to consider about the size of the records:
• Right now, a note cannot exceed 65k characters in ArchivesSpace. The
overall file might not even be that large, but if you have any really, really,
Hi Nic,
I can’t speak to reports, but as for the ArchivesSpace Public User Interface,
published accession records will always show up right now. In other words,
until the “Publish?” checkbox is not selected, it gets indexed in the PUI.
We’ve just started publishing accession records in one of
. ( Because
making changed directly in MySQL bypasses the indexer notifications. ) Also a
lot more efficient if you’ve got a lot of resources.
— Steve.
On Aug 2, 2018, at 2:56 PM, Custer, Mark
mailto:mark.cus...@yale.edu>> wrote:
That’s actually a really good use case for using the ASpa
e_users_group-boun...@lyralists.lyrasis.org>
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
On Behalf Of Custer, Mark
Sent: Thursday, August 02, 2018 11:00 AM
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Arc
Rachel,
Yep, it looks like that’s a new bug that you’ve uncovered and diagnosed (I’ve
also seen something strange happening with the container3/grandchild container
filters on those pages, but I haven’t gone back to investigate what’s going on
there just yet).
I just confirmed the same
Thomas,
If you could send me a copy of the EAD file, I can take a look this afternoon
(I'm working on a new process to create PDF files in ASpace using the new EAD3
export option, but I have the current ASpace PDF files handy for testing).
The issue is definitely that the current EAD to PDF
template really only
expects physdesc elements with a single extent child.
Mark
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Custer, Mark
Sent: Friday, 22 June, 2018 8:50 AM
To: Archivesspace Users Group
John,
What I think that you'd want to do in this case is to modify the EAD so that it
looks like the following:
15.0 linear_feet
(36 boxes + oversize folder)
Two important points about this:
1. The ASpace EAD importer uses the database values for controlled value
fields, which is why
Brian, Tim:
In my opinion, the entire digital object module deserves a review, and that
would include both EAD imports and exports (in those exports, for example, the
digital object title is repeated as both an @xlink:title AND a daodesc/p; and
worse yet, the ASpace required identifier isn't
Hopefully someone else can chime in with an actual answer about how to do this
via a plugin, but outside of the views, I've had more success overriding things
in the PUI with a custom build. And with the citation feature, you might also
need to check out this bit, which is where the URL +
All,
To follow up on this thread, and in case it helps anyone else, here's an
example configuraiton that I just tested since I needed to implement a similar
configuration and ran into a few issues the first time around:
AppConfig[:pui_hide][:accession_badge] = true
Rachel, all:
It was documented in the plugin. I still refer to that documentation here:
https://github.com/hudmol/container_management#configuring-it
But it should be added to the core documentation, of course!
Mark
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
Celia,
I wish that this could’ve been accomplished with the initial release of the
PUI, but there were a number of issues that didn’t allow that to happen (and
I’m not sure of all of the technical issues, to be quite honest).
However, at Yale, we will be setting up re-directs from our current
Lydia,
See the very last section, Identifier Encoding, at the bottom of this page:
https://guides.library.yale.edu/archivesspace/ASpaceContainerManagement This
is documentation from the original top container plugin, but the same holds
true now in the core code.
Things will look much looker
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
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
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
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:
[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 <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF
S
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,
1 - 100 of 133 matches
Mail list logo
