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
rasis.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 Interface
Hi, Lara.
Depending on
[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 new
ArchivesSpace PUI
Dear
cDmVxLGTIl3XCIWNtmmSP1vh96Z0r-hkqodUzf7hdQ=740yfwjw57gZhC04Vk5w8GWaCFjTpYbv21AnaIKmWzg=>
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: Archi
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, November 22, 2016 12:56 PM
To: A
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
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
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,
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
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.
is checked.
Regards,
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: Arc
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
lto:archivesspace_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
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_g
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
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
sspace_users_group-boun...@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 <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_G
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
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:
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
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
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:
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:
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 -->
that 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 <archivesspace_users_gr
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
ewski / UVA Alderman Library
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
<archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Custer,
Mark <mark.cus...@yale.edu>
Sent: Wednesday, August 30, 2017 1:51:42 PM
To: archivesspace_users
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
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
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
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
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
s.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
on behalf of Custer, Mark <mark.cus...@yale.edu<mailto:mark.cus...@yale.edu>>
Sent: Wednesday, August 23, 2017 1:52:50 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error when sear
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
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
[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,
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:
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
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 +
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
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
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
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
. ( 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
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
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
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
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,
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”
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:
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
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
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
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
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.
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,
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
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
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
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
...@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
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
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
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
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
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
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
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
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).
:
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
).
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":
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
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
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
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
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
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
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,
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
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
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:
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
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
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
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
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
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
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
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
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,
1 - 100 of 133 matches
Mail list logo
