Re: [Archivesspace_Users_Group] Detailed data map for LCNAF plug-in?

[Bowers, Kate A.]

For anyone else who is interested in this, there might not be documentation, 
but the "map" part of the converter code is here (thanks Steven Majewski):
https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_auth_agent_base_map.rb

It takes quite a bit of mucking around to see where the data is going, but it 
is possible to figure it out.

Kate


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Bowers, 
Kate A.
Sent: Thursday, May 26, 2022 12:21 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Detailed data map for LCNAF plug-in?

Does anyone know where I can find a list of exactly which fields from LCNAF 
authority records go into which fields in AS agent records if one implements 
the LCNAF plug-in?

I've search git-hub and the AS wiki'd and AS help and I have not found details 
on exactly what the import does.

Thanks!

Kate
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Items not showing up in search results filter

[Anna Haywood]

Hello Andrew,

Thanks so much for your answer. Yes, I am in the right repository and your 
technique of searching * brought up the items I was looking for. However, for 
some collections, when I search their unique ID, then filter by "archival 
object," I can see the item filter. But for others, the items don't come up. I 
am trying to figure out what the difference between these collections are or 
the difference between the item records in each fonds but so far I am at a loss.

Anna


---

Anna Haywood
Archiviste
Archivist

Centre Canadien d'Architecture
Canadian Centre for Architecture
1920, rue Baile, Montréal, Québec, Canada, H3H 2S6
+1 5149397001x1368
cca.qc.ca
Twitter | 
Instagram | 
Facebook | 
YouTube

Comment pouvons-nous contribuer à une approche plus collaborative du travail 
archivistique 
transnational?
How can we contribute to a collaborative approach to transnational archival 
work?

Inscrivez-vous
 pour recevoir de nos nouvelles.
Sign 
up
 to get news from us.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: Thursday, May 19, 2022 3:42 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Items not showing up in search results 
filter


Presumably you are in the correct repository, otherwise your search for a 
particular collection wouldn't find anything. Is it a problem with just one 
specific collection, or all of them? If you don't do the search for a unique ID 
first, and instead just do a simple search for *, then filter to archival 
objects, do you still not get the "Item" option in Level facet?

You could try a soft re-index, to rule out it being a problem with Solr being 
out-of-sync with MySQL:

https://archivesspace.github.io/tech-docs/administration/indexes.html

Andrew.


On 18/05/2022 21:49, Anna Haywood wrote:
Hello everyone,

I am having some trouble with my search results filters. When I search by 
collection unique ID in ArchivesSpace and then filter by "archival object" on 
the left hand side, I receive an additional set of filters for "Level." Here I 
can filter by series, subseries, file, etc. However, for some time now, the 
level "item" does not show up as one of the filters. This is very odd because 
in my sandbox environment, the items does come up as an option in the Level 
filter. Both sandbox and production are on version 3.2.0.

Does anyone have any theories about why this might be happening?

Thanks in advance,
Anna

---

Anna Haywood
Archiviste
Archivist

Centre Canadien d'Architecture
Canadian Centre for Architecture
1920, rue Baile, Montréal, Québec, Canada, H3H 2S6
+1 5149397001x1368
cca.qc.ca
Twitter
 | 
Instagram
 | 

[Archivesspace_Users_Group] Customizing the accessions template

[McLaughlin, Brianna Jean]

Hi everyone,

We are starting to look into the Accessions module. The Accessions template 
looks pretty simple compared to the Harvard spreadsheet template we're using 
for importing components. Is it still possible to customize the spreadsheet 
without preventing a successful import? For example, could we add Agent fields 
by copy and pasting and adding a "_2"? Could we add more Event fields by 
following the same structure (ie accessions_deaccession_date). Generally, I'd 
love to hear any experimentation with customizing the Accessions template and 
what limits you've encountered.

We're on AS version 2.7.1, likely to be upgrading soon to 3.?

Thanks in advance!

Bri McLaughlin, she/her/hers
Visiting Metadata Services Librarian
Indiana University
812-856-3321

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace

[Ron Van den Branden]

Thanks for that pointer, Cory! I’m probably a tad late at that party to give my 
support, though it seems like a useful idea (from a user perspective).

Best,

Ron

Van: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 Namens Cory Nimer
Verzonden: woensdag 25 mei 2022 17:15
Aan: Archivesspace Users Group 
Onderwerp: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

Ron,

I would agree that it would be preferable to have a more EAD3-friendly 
configuration for related materials notes, at least in order to reduce/remove 
the need for mixed content within these notes. I don't know if there is 
widespread interest in moving implementing something more like the Agents 
module's Sources subrecord or the Metadata Rights Declarations with their 
fields for recording a descriptive note and a URL separately. It looks like the 
project has already rejected the idea of being allowing linking between 
different records within the database, though (ANW-763; 
https://archivesspace.atlassian.net/browse/ANW-763).

Best,

Cory Nimer
University Archivist
Brigham Young University

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Wednesday, May 25, 2022 10:05 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

Hi Corey,

Many thanks for your helpful reply! In our current data, these structured links 
are indeed connected to a field that maps to  in 
ArchivesSpace, so that’s indeed the destination we had in mind.

Your example for embedding ArchivesSpace-internal links via the ArchivesSpace 
ID for a @href attribute was really helpful and finally made me get it working 
in the test instance, great! That’s a useful mechanism, though I fully agree 
the manual input process is brittle, even with the (limited) “mixed content” 
completion help. In order to make the most semantic sense, as you exemplified 
with the  example, our colleagues and volunteers describing the 
archives would have to be knowledgeable of XML syntax rules, and the suitable 
EAD structures for the information they’d want to enter. Yet, even if a new 
structured resource-to-resource link field would be too far off the 
implementation horizon, perhaps a general improvement for adding such internal 
cross-links in text fields in a more guided way could be of interest. I’ll 
think about it!

Finally, your data audit remark sounds intriguing and -considering the amount 
of data cleanup this data migration project has confronted us with- a vital 
part of best practice. Would you mind elaborating on that, or pointing me to 
any available documentation?

Best,

Ron

Van: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 Namens Corey Schmidt
Verzonden: woensdag 25 mei 2022 14:57
Aan: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Onderwerp: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

Hey Ron,

Glad to see you reaching out! I’m not sure if others have emailed you regarding 
this, so I’ll put in my 2 cents worth.

  *   From what I understand, there is no mechanism within ArchivesSpace that 
provides a structured “Agents/Related Accessions” type link from one resource 
to another, nor one archival object to another.
  *   Have you considered using the “Related Materials” note 
()?
 The advantage with this is the note is made specifically for related materials 
either within the repository or without and you don’t need a full URL, just the 
ArchivesSpace ID if you’re using the PUI, like so: Related Collection title. The 
problem with this is you have to enter the info by hand, which is error prone 
(we’ve scheduled a yearly “data audit” to help us catch errors like these).
  *   I don’t know of any institution that has developed a 
plugin, nor is this on 
the roadmap I think. Nevertheless, you can submit a JIRA 
ticket
 for this feature (how to do that linked 
here)
 – explaining how you want it to work with as much detail as possible. The 
Development Priority Team will then determine if the ArchivesSpace development 
team or community can/should prioritize it in future releases. The more 
attention a ticket gets (comments, clarifications, etc.) the more likely it is 
to 

[Archivesspace_Users_Group] Take a Break with ArchivesSpace goes on hiatus after May 27

[Jessica Crouch]

ArchivesSpace users,


Join us tomorrow for our final Break with ArchivesSpace before these breaks go 
on hiatus. We may revive the breaks in some form in the future, but until then 
we look forward to seeing you tomorrow.  Thanks to everyone who has joined us 
at our standing Friday break calls.  It’s been great reconnecting with so many 
familiar faces and getting to know so many new faces as well.


We will host the final Break with ArchivesSpace this Friday (May 27th) via zoom 
at 12pm ET. There is no agenda or presentation developed for this call. We just 
want to provide an opportunity to connect, chat and recharge. Use this as a 
time to get help or talk about ArchivesSpace (or anything else) in an informal 
setting or just have a beverage with other ArchivesSpace users during this 
stressful time.


Register to join at 
https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv


We seek to provide a welcoming, fun, and safe community experience for 
everyone. The full text of the code of conduct is available at 
https://archivesspace.org/archivesspace-code-of-conduct.


Please email 
archivesspaceh...@lyrasis.org with any 
questions.
We hope to see you tomorrow!

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org




___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace

[Ron Van den Branden]

Whoa, thanks for sharing both your code and those pointers, Corey! That’s study 
stuff for when the dust’ll have settle a bit.

I’ll present the current option for internal linking in ArchivesSpace to our 
colleagues and IT partner; if this leads to structured suggestions for 
improvement, it would be great if that could result in a Jira ticket. Many 
thanks in advance for your support.

Best,

Ron


Van: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 Namens Corey Schmidt
Verzonden: woensdag 25 mei 2022 17:29
Aan: Archivesspace Users Group 
Onderwerp: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

Ron,

My pleasure! I’m glad the example helped get you going for your test instance. 
Thanks for the follow-up Cory. It’s a shame that functionality was rejected, 
but understandable.

As you pointed out Ron, it’s still a brittle process, not helped by the fact 
that it’s sometimes difficult to ask colleagues/volunteers to familiarize 
themselves with XML syntax and EAD tags and attributes. If after considering 
improvements for internal cross-links you want to post a ticket and need/want 
help, just let me know! I’m happy to make suggestions and give a +1.

Sure, after migrating to ArchivesSpace, we compiled a bunch of tests we did for 
checking our data. I wrote a python 
script
 to do the tests, create a spreadsheet with the results, email those results to 
our users, and I worked with our sysadmin to make a cron job to run the script 
once a year. It checks:

  *   controlled vocabularies for non-permitted terms
  *   resources/items with Component Unique IDs (we don’t use them)
  *   containers with no barcodes or indicators
  *   archival objects with multiple containers or digital objects
  *   archival objects falsely labeled as “collection” level
  *   EAD-IDs (we make these in our EAD.xml exporter)
  *   duplicate subjects and agents
  *   archival objects on the same level but have different labels (i.e. a file 
and series on the same level together)
  *   XML errors
  *   URL errors

With a little programming knowledge, you could modify this script or make one 
yourself. There’s also a number YouTube videos on data cleanup in 
ArchivesSpace: ArchivesSpace Data Cleanup Webinar: Tips, Tricks, and 
Tools, How to Make Technology Work 
for You In an ArchivesSpace Data Cleanup 
Project, Someday is Here! 
ArchivesSpace Projects for Working from 
Home.

Corey

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Cory Nimer
Sent: Wednesday, May 25, 2022 11:15 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Ron,

I would agree that it would be preferable to have a more EAD3-friendly 
configuration for related materials notes, at least in order to reduce/remove 
the need for mixed content within these notes. I don't know if there is 
widespread interest in moving implementing something more like the Agents 
module's Sources subrecord or the Metadata Rights Declarations with their 
fields for recording a descriptive note and a URL separately. It looks like the 
project has already rejected the idea of being allowing linking between 
different records within the database, though (ANW-763; 
https://archivesspace.atlassian.net/browse/ANW-763).

Best,

Cory Nimer
University Archivist
Brigham Young University

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Wednesday, May 25, 2022 10:05 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] linking to related Resources / 
Archival Objects in ArchivesSpace

Hi Corey,

Many thanks for your helpful reply! In our current data, these structured links 
are indeed connected to a field that maps to  in 
ArchivesSpace, so that’s indeed the destination we had in mind.

Your example for embedding ArchivesSpace-internal links via the ArchivesSpace 
ID for a @href attribute was really helpful and finally made me get it working 
in the test instance, great! That’s a useful mechanism, though I fully agree 
the manual input process is brittle, even with the (limited) “mixed content” 
completion help. In order to make the most semantic sense, as you exemplified 
with the  example, our colleagues and volunteers 

[Archivesspace_Users_Group] Detailed data map for LCNAF plug-in?

[Bowers, Kate A.]

Does anyone know where I can find a list of exactly which fields from LCNAF 
authority records go into which fields in AS agent records if one implements 
the LCNAF plug-in?

I've search git-hub and the AS wiki'd and AS help and I have not found details 
on exactly what the import does.

Thanks!

Kate
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Unable to launch ArchivesSpaceService

[Allhiser, Ivan]

Hello all,

Our previous system administrator set up ArchivesSpace 2.8.1 and we received a 
ticket that it needed to be re-indexed. None of us were even aware of what this 
server did. Before I could access it, the server needed to be rebooted. Once it 
came back up, I was unable to start the ArchivesSpaceServe. I am shown this 
error whenever I try (even with Powershell)

"Windows could not start the ArchivesSpaceService on Local Computer. For more 
information, review the System Event Log. If this is a non-Microsoft service, 
contact the service vendor, and refer to service-specific error code 5."

I've checked the System Event Long and I don't even see any events that show an 
attempt to start the service. We've checked the logs and honestly, I'm lost 
trying to swim through all this data. I don't see anything standing out that 
says there's an error. Has anyone encountered this before and know of a fix?

Thank you for your time,
Ivan Allhiser
System Administrator
Information Technology Services
[Dining Services | Avila University]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Issue with gems extensions ( sassc, bindex, ... ) on Mac with 3.2.0

[Brian Hoffman]

Hi Steve,

This is a known unresolved issue – ArchivesSpace is built on Jruby, the premise 
being that it can sit entirely on the JVM and thus be portable as any Java app. 
But over the years various gems with extensions have crept into the application 
and broken that model – in the case of the sassc gem, we have actually been 
copying over the gem that was built in the 2.8.1 release to all subsequent 
releases because for some reason that one seems to work on most systems. I 
think the proper solution would be to eliminate gems that depend on c 
extensions, and figuring out a way to do that is one of the objectives of our 
next Rails environment upgrade. Suggestions from those who are smarter than me 
on how to resolve this are most welcome.

Brian

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Majewski, Steven Dennis (sdm7g) 
Date: Monday, May 23, 2022 at 2:37 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Issue with gems extensions ( sassc, 
bindex, ... ) on Mac with 3.2.0

I usually test out migrations and local plugins on my Mac laptop first before 
installing on a test server.
I ran into a couple of issues with 3.2.0 release.

Using the release downloaded from
https://github.com/archivesspace/archivesspace/releases/tag/v3.2.0

Backend and frontend appeared to work and communicate with the separately 
installed Solr instance however the PUI gave system errors from the bundler 
relating to sassc-2.4.0

Looking at the log file, there were a number of messages about that and other 
gems:

Ignoring bindex-0.8.1 because its extensions are not built. Try: gem pristine 
bindex --version 0.8.1
Ignoring llhttp-ffi-0.3.1 because its extensions are not built. Try: gem 
pristine llhttp-ffi --version 0.3.1
Ignoring sassc-2.4.0 because its extensions are not built. Try: gem pristine 
sassc --version 2.4.0
I attempted to run ‘gem pristine’ after setting GEM_HOME, which seemed to do 
something, but didn’t fix the  issue. ( Doing these sorts of fixes are a bit 
confusing due to the way that JRuby is packaged in ArchivesSpace, so I may not 
have been doing it correctly. )

I finally tried building my own distribution from GitHub tag v3.2.0, and 
unpacking that zip file and running it appears to work ( so far! Still indexing 
PUI )

So I’m guessing that there is something in these gem extensions that is 
architecture or java version specific and the distributions on GitHub are not 
universal.

We may require a fixup script that runs the bundler similar to the way it’s 
done in initialize-plugins script.

Has anyone else run into this issue ?

— Steve Majewski


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group