date:20220616

Re: [Archivesspace_Users_Group] material type plugin : translation missing error

2022-06-16 Thread Rajitha Mallempati

Hi Blake,

Can you please tell me how can I do that? I tried by adding material_types
tooltip: | line in locales/en.yml file but it’s not working.

Thanks,
rr40


On Thu, Jun 16, 2022 at 11:33 AM Blake Carver 
wrote:

> That plugin hasn't been updated in a lonng time. Assuming it still
> even works, it looks like you can add that missing value to your locales:
>
>
> https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/common/locales/LOCALES_README.md
> --
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> Rajitha Mallempati 
> *Sent:* Wednesday, June 15, 2022 4:28 PM
> *To:* Archivesspace_Users_Group@lyralists.lyrasis.org <
> Archivesspace_Users_Group@lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] material type plugin : translation
> missing error
>
> Hello all,
>
> I am a student working at the University of delaware. I really need help
> with the translation issue that I am getting after adding the material
> types plugin-v1.5 to the archivesspace-v3.1.1. We are running archivesspace
> as a service.
>
> For testing I created a dummy accession on local machine. I can
> successfully open staff and public interfaces but the material types plugin
> is not working as it supposed to.
> I am getting the following error message on the left side of the staff
> interface :
>
>- Basic Information
>
>- Languages
>
>- Dates 
>- Extents 
>- Agent Links
>
>- Related Resources
>
>- Related Accessions
>
>- Subjects
>
>- External Documents
>
>- Rights Statements
>
>- Metadata Rights Declarations
>
> 
>- Instances
>
>- Deaccessions
>
>- Collection Management
>
>- Classifications
>
>- User Defined
>
>- translation missing: plugins.material-types._plural
>
>-
>
>
> how to resolve the translation missing error. Please help me
>
> Thanks,
> rr40
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

2022-06-16 Thread Blake Carver

Did you make any other changes to the config.rb file that might be changing up 
the logging?
I'm not really sure what might be wrong, this is one of those things that 
always "just works" and I don't know what could be wrong.
You're sure it's even running?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Thursday, June 16, 2022 11:36 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake, and apologies -- I meant to say config.rb (not 
config-defaults.rb). Even with the suggested debug settings in place in 
config.rb, our Archivesspace instance doesn't produce error logging.

We are running an Archivesspace v3.2.0 release we built + local changes in 
locales and plugins. It was built on RHEL 7.9 with OpenJDK 11.0.14.1. All of 
our AppConfig[:_log_level] are set to "debug" in our config.rb.  All of the 
log destinations are set to "default".

There is an archivesspace.out file in the /logs directory, but it only contains 
startup info and a few warnings and is not modified as frequently as we would 
expect. As the archivesspace.out file does have some things written to it, 
there does not seem to be a write permissions error. We would expect there to 
be additional logging because we are encountering errors in the PUI.

Thanks again for any help,
Wendy

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 8, 2022 1:25 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Running in production mode means downloading and running the release, not the 
source code
https://github.com/archivesspace/archivesspace/releases/download/v3.2.0/archivesspace-v3.2.0.zip

Changing configuration variables would then be done in config.rb not 
config-defaults.rb.

Your archivesspace.out log file should then end up in the /logs/ directory.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Wednesday, June 8, 2022 12:26 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake. We checked our config-defaults.rb, and those lines match what 
you linked to. So it seems like we've set the log levels to DEBUG, but we're 
still not seeing any error messages being logged. Is there something else we 
should check that might be getting in the way of the logs?

Here's what we have for those lines in config-defaults.rb :

57 AppConfig[:frontend_log] = "default"
59 AppConfig[:frontend_log_level] = "debug"

61 AppConfig[:backend_log] = "default"
62 AppConfig[:backend_log_level] = "debug"

64 AppConfig[:pui_log] = "default"
65 AppConfig[:pui_log_level] = "debug"

67 AppConfig[:indexer_log] = "default"
68 AppConfig[:indexer_log_level] = "debug"

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Tuesday, June 7, 2022 1:20 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

You can set the log levels to DEBUG here
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64

Keep in mind that on version 3.2 you'll have Solr stuff being written into the 
sperate Solr server logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Tuesday, June 7, 2022 12:59 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Hi Blake,

When running ASpace (3.2.0) in production mode (as opposed to development 
mode), should we be seeing information in our error logs?

We are preparing to go live with 3.2.0. After testing 3.2.0 in development 
mode, we want to test our stage instance of ASpace 3.2.0 in production mode to 
mimic what our production instance will look like. We aren't getting any info 
from the logs in production mode, making it difficult to troubleshoot. Is there 
a way we can enable logs in production mode?

Thank you,
Wendy

Wendy Hagenmaier
Digital Curation Archivist
Service Owner, University Archives & Special Collections Repository and 
retroTECH
Archives, Records Management, and Digital Curation
Georgia Tech Library
Atlanta, GA 30332
wendy.hagenma...@library.gatech.edu
Pronouns: she/her

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 1, 2022 5:02 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspa

Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to backend" error

2022-06-16 Thread Blake Carver

> Indicates a deprecation in the JDBC call, AND YET it successfully checks the 
> tables and confirms they are set to UTF-8.
> I am using the latest MySQL Connector jar for this:  
> mysql-connector-java-8.0.29.jar for Ubuntu

Yep, that's fine I think.

> It's just so weird to me that the JDBC connection seems to be working, yet 
> "can't connect to backend".

The problem is " undefined method `[]' for nil:NilClass " it's expectig a value 
there and it's not getting one. Did something change in the DB? Upgrade or 
something else that changed things?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mark 
Cyzyk 
Sent: Wednesday, June 15, 2022 9:01 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to 
backend" error

More on this.

>From the log:

ArchivesSpaceThreadDump: Touch the file 
'/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump
I, [2022-06-15T11:54:40.827499 #9472]  INFO -- : Thread-2000: Connecting to 
database: 
jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8.
 Max c>
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class 
is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the 
SPI and manual loading of the driver class is genera>
I, [2022-06-15T11:54:42.592887 #9472]  INFO -- : Thread-2000: All tables 
checked and confirmed set to UTF-8.  Nice job!

  A trace file has been written to the following location: 
/usr/share/archivesspace/data/tmp/aspace_diagnostic_1655294083.txt

  This file contains information that will assist developers in diagnosing
  problems with your ArchivesSpace installation.  Please review the file's
  contents for sensitive information (such as passwords) that you might not
  want to share.

Jun 15, 2022 11:54:43 AM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: An exception happened during JRuby-Rack startup
undefined method `[]' for nil:NilClass
--- System
jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK 64-Bit Server VM 25.312-b07 
on 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 +jit [linux-x86_64]
Time: 2022-06-15 11:54:43 +
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

Indicates a deprecation in the JDBC call, AND YET it successfully checks the 
tables and confirms they are set to UTF-8.

I am using the latest MySQL Connector jar for this:  
mysql-connector-java-8.0.29.jar for Ubuntu

It's just so weird to me that the JDBC connection seems to be working, yet 
"can't connect to backend".

>From the trace file:

 "exception": {
"msg": "undefined method `[]' for nil:NilClass",
"backtrace": [
  "uri:classloader:/record_inheritance.rb:31:in `block in prepare_schemas'",
  "org/jruby/RubyArray.java:1735:in `each'",
  "uri:classloader:/record_inheritance.rb:16:in `block in prepare_schemas'",
  "org/jruby/RubyHash.java:1350:in `each'",
  "uri:classloader:/record_inheritance.rb:15:in `prepare_schemas'",

"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:108:in
 `block in ArchivesSpaceService'",

"/usr/share/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in 
`configure'",

"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79:in
 `'",

"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39:in
 `'",
  "org/jruby/RubyKernel.java:956:in `require'",

"uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in
 `require'",

"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in
 `block in (root)'",
  "org/jruby/RubyBasicObject.java:1691:in `instance_eval'",

"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in
 `(root)'",
  "uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `'",
  "launcher/launcher.rb:92:in `start_server'",
  "launcher/launcher.rb:157:in `main'",
  "launcher/launcher.rb:261:in `'"
]
  }
}

Advice appreciated!  Again, all I'm trying to do is duplicate our ASpace in 
Vagrant.

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

On 6/11/22 17:08, Mark Cyzyk wrote:
All,

I am trying to duplicate our Archivesspace production app in a local Vagrant 
box.

I am getting an "unable to connect to backend" er

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

2022-06-16 Thread Hagenmaier, Wendy L

Thanks, Blake, and apologies -- I meant to say config.rb (not 
config-defaults.rb). Even with the suggested debug settings in place in 
config.rb, our Archivesspace instance doesn't produce error logging.

We are running an Archivesspace v3.2.0 release we built + local changes in 
locales and plugins. It was built on RHEL 7.9 with OpenJDK 11.0.14.1. All of 
our AppConfig[:_log_level] are set to "debug" in our config.rb.  All of the 
log destinations are set to "default".

There is an archivesspace.out file in the /logs directory, but it only contains 
startup info and a few warnings and is not modified as frequently as we would 
expect. As the archivesspace.out file does have some things written to it, 
there does not seem to be a write permissions error. We would expect there to 
be additional logging because we are encountering errors in the PUI.

Thanks again for any help,
Wendy

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 8, 2022 1:25 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Running in production mode means downloading and running the release, not the 
source code
https://github.com/archivesspace/archivesspace/releases/download/v3.2.0/archivesspace-v3.2.0.zip

Changing configuration variables would then be done in config.rb not 
config-defaults.rb.

Your archivesspace.out log file should then end up in the /logs/ directory.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Wednesday, June 8, 2022 12:26 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake. We checked our config-defaults.rb, and those lines match what 
you linked to. So it seems like we've set the log levels to DEBUG, but we're 
still not seeing any error messages being logged. Is there something else we 
should check that might be getting in the way of the logs?

Here's what we have for those lines in config-defaults.rb :

57 AppConfig[:frontend_log] = "default"
59 AppConfig[:frontend_log_level] = "debug"

61 AppConfig[:backend_log] = "default"
62 AppConfig[:backend_log_level] = "debug"

64 AppConfig[:pui_log] = "default"
65 AppConfig[:pui_log_level] = "debug"

67 AppConfig[:indexer_log] = "default"
68 AppConfig[:indexer_log_level] = "debug"

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Tuesday, June 7, 2022 1:20 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

You can set the log levels to DEBUG here
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64

Keep in mind that on version 3.2 you'll have Solr stuff being written into the 
sperate Solr server logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Tuesday, June 7, 2022 12:59 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Hi Blake,

When running ASpace (3.2.0) in production mode (as opposed to development 
mode), should we be seeing information in our error logs?

We are preparing to go live with 3.2.0. After testing 3.2.0 in development 
mode, we want to test our stage instance of ASpace 3.2.0 in production mode to 
mimic what our production instance will look like. We aren't getting any info 
from the logs in production mode, making it difficult to troubleshoot. Is there 
a way we can enable logs in production mode?

Thank you,
Wendy

Wendy Hagenmaier
Digital Curation Archivist
Service Owner, University Archives & Special Collections Repository and 
retroTECH
Archives, Records Management, and Digital Curation
Georgia Tech Library
Atlanta, GA 30332
wendy.hagenma...@library.gatech.edu
Pronouns: she/her

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 1, 2022 5:02 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

 https://archivesspace.github.io/tech-docs/development/dev.html
That explains the development mode.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Duckett, 
Brian (NIH/NLM) [C] 
Sent: Wednesday, June 1, 2022 4:45 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] 
; Kalyanasundaram, Sriram (NIH/NLM) [C] 

Subject: [Archivesspace_Users_Group] Requesting

Re: [Archivesspace_Users_Group] material type plugin : translation missing error

2022-06-16 Thread Blake Carver

That plugin hasn't been updated in a lonng time. Assuming it still even 
works, it looks like you can add that missing value to your locales:

https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/common/locales/LOCALES_README.md

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Rajitha 
Mallempati 
Sent: Wednesday, June 15, 2022 4:28 PM
To: Archivesspace_Users_Group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] material type plugin : translation missing 
error

Hello all,

I am a student working at the University of delaware. I really need help with 
the translation issue that I am getting after adding the material types 
plugin-v1.5 to the archivesspace-v3.1.1. We are running archivesspace as a 
service.

For testing I created a dummy accession on local machine. I can successfully 
open staff and public interfaces but the material types plugin is not working 
as it supposed to.
I am getting the following error message on the left side of the staff 
interface :
  *   Basic Information 

  *   Languages 

  *   Dates 
  *   Extents 
  *   Agent Links 

  *   Related Resources 

  *   Related Accessions 

  *   Subjects 
  *   External Documents 

  *   Rights Statements 

  *   Metadata Rights Declarations 

  *   Instances 
  *   Deaccessions 

  *   Collection Management 

  *   Classifications 

  *   User Defined 

  *   translation missing: 
plugins.material-types._plural
  *

how to resolve the translation missing error. Please help me

Thanks,
rr40

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

Re: [Archivesspace_Users_Group] PDF export with a logo

2022-06-16 Thread Blake Carver

I've seen 2 things cause this

  1.  Just do a reindex, seems like sometime it just needs a kick in the 
indexes for some reason.
  2.  The server hosting that image is blocking access so ArchivesSpace can't 
grab that file. It's usually this.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 松山　ひとみ 

Sent: Thursday, June 16, 2022 12:23 AM
To: 'Archivesspace_Users_Group@lyralists.lyrasis.org' 

Subject: [Archivesspace_Users_Group] PDF export with a logo


Hello.



We've set up our museum logo in the repository field "Branding Image URL," with 
the URL; http://(--- ArchivesSpace URL ---)/assets/images/logo.jpg.

However, our logo doesn't appear on the cover page of an exported PDF from the 
SUI. The PDF was generated through the function; export -> generate pdf, which 
follows the path, Resource -> EAD -> xsl -> fop -> PDF.



Is there anything wrong with our logo data, or should we miss anything in the 
process?



We’d appreciate your kind help!



Hitomi Matsuyama, Audiovisual Archivist



Nakanoshima Museum of Art, Osaka

4-3-1 Nakanoshima, Kita-ku

Osaka 530-0005 JAPAN

tel. +81 (0)6 64 79 05 58

email. matsuyam...@nakka-art.jp


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

Re: [Archivesspace_Users_Group] finding aid template?

2022-06-16 Thread Leah Tams

Hi Tess,

You might consider taking advantage of the Default Values feature in ASpace—it 
allows you to set up a template record that pre-populates the fields of your 
choosing. Here is a link to a helpful document from the Orbis Cascade Alliance: 
https://drive.google.com/file/d/1GjSoZlocBRlt7uDCqbduF4TUgopfNcc9/view. 
Pertinent information begins on page 10, with the heading “Pre-Populating 
Fields with Default Values.” It is particularly useful for standardizing notes, 
as well as providing instructions within a field. We only use it for Resource 
records at Duke, but it can also be used for Accession records.

I hope this is helpful! Happy to chat more if you’d like.

Best,
Leah

she/her/hers
MSLS in Archives & Records Management
Accessions Coordinator
Rubenstein Rare Book & Manuscript Library
Duke University
leah.t...@duke.edu | 
leahtams.org

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tessa 
Wakefield
Sent: Thursday, June 16, 2022 11:19 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] finding aid template?

Hello! We're in the middle stages of migrating our finding aids into 
ArchivesSpace using the load via spreadsheet option, which is working great. 
We're thinking ahead to future practices for finding aids -- currently, we 
draft them in google docs and copy / paste them into our existing finding aid 
system (Drupal). I don't think this is going to be the most efficient going 
forward.

Does anyone use a finding aid template that they can ingest directly into 
ArchivesSpace? Curious to learn more about how institutions actively using the 
system create their finding aids!

Many thanks,
Tess

--
Tessa Wakefield 
(she/her)

Archival Processor & Reference Associate
Rod Library

319-273-2132

LIB 342  /  Cedar Falls, IA 50614
uni.edu
  /  #1UNI
To schedule an appointment, please visit 
LibCal.
[UNI / University of Northern Iowa]








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

[Archivesspace_Users_Group] finding aid template?

2022-06-16 Thread Tessa Wakefield

Hello! We're in the middle stages of migrating our finding aids into
ArchivesSpace using the load via spreadsheet option, which is working
great. We're thinking ahead to future practices for finding aids --
currently, we draft them in google docs and copy / paste them into our
existing finding aid system (Drupal). I don't think this is going to be the
most efficient going forward.

Does anyone use a finding aid template that they can ingest directly into
ArchivesSpace? Curious to learn more about how institutions actively using
the system create their finding aids!

Many thanks,
Tess

-- 
*Tessa Wakefield (she/her )*

Archival Processor & Reference Associate
Rod Library

319-273-2132

LIB 342  /  Cedar Falls, IA 50614
uni.edu  /  #1UNI
*To schedule an appointment, please visit **LibCal
.*
[image: UNI / University of Northern Iowa]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] material type plugin : translation missing error

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to backend" error

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

Re: [Archivesspace_Users_Group] material type plugin : translation missing error

Re: [Archivesspace_Users_Group] PDF export with a logo

Re: [Archivesspace_Users_Group] finding aid template?

[Archivesspace_Users_Group] finding aid template?

8 matches

Site Navigation

Mail list logo

Footer information