Re: [Archivesspace_Users_Group] Archivesspace dropping https in Staff UI

[Trevor Thornton]

I'm bad at this, but my understanding is that those redirects are more for
making sure people who try to use old URLs end up at the right place.

The settings described here:
https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#setting-up-ssl
are doing most of the work, and AppConfig[:frontend_proxy_url] is used
internally to make sure that AS generates correct links from the list view
(search results, etc.) to a single record view.



On Fri, Aug 30, 2019 at 11:26 AM Kara Hart  wrote:

> Cont. thoughts from last email...
> In fact, it looks like my System staff didn't add the redirects to the
> apache config files.
>
> If I added these lines to that config, would that possibly fix the
> problem?
>
> 
> ServerName archivesstaff.wellesley.edu
> RewriteEngine On
> RewriteCond %{HTTPS} off
> RewriteRule (.*) https://archivesstaff.wellesley.edu$1 [R,L]
> 
>
> 
> ServerName archives.wellesley.edu
> RewriteEngine On
> RewriteCond %{HTTPS} off
> RewriteRule (.*) https://archives.wellesley.edu$1 [R,L]
> 
>
>
> Thanks, Kara
>
> ~~~ Kara S. Hart
>
> Systems Librarian - Library & Technology Services - Wellesley College
>
>
>
> On Fri, Aug 30, 2019 at 10:55 AM Kara Hart  wrote:
>
>> I've tried these three different settings.
>>
>> AppConfig[:frontend_proxy_url] = "https://archivesstaff.wellesley.edu;
>> AppConfig[:public_proxy_url] = "https://archives.wellesley.edu;
>>
>> AppConfig[:frontend_proxy_url] = proc { "
>> https://archivesstaff.wellesley.edu; }
>> AppConfig[:public_proxy_url] = proc { "https://archives.wellesley.edu; }
>>
>> AppConfig[:frontend_proxy_url] = proc { AppConfig[:
>> https://archivesstaff.wellesley.edu] }
>> AppConfig[:public_proxy_url] = proc { AppConfig[:
>> https://archives.wellesley.edu] }
>>
>> The last broke AS launching, which makes sense.  I think the default is
>> to use AppConfig[:frontend_url]
>> which is AppConfig[:frontend_url] = "http://localhost:8080; by default.
>>
>> I wonder if that is it.  Because before we made this change the link to
>> the staff interface from the public interface was http://localhost:8080
>> and never rendered.  I wonder if there's another apache setting I need for
>> localhost?
>>
>>
>>
>> ~~~ Kara S. Hart
>> Systems Librarian - Library & Technology Services
>> -
>> Wellesley College
>>
>>
>> On Fri, Aug 30, 2019 at 9:04 AM Trevor Thornton 
>> wrote:
>>
>>> I think these are the settings in config.rb that make that work
>>> correctly (from the documentation):
>>> AppConfig[:frontend_proxy_url] = "https://staff.myarchive.org;
>>> AppConfig[:public_proxy_url] = "https://public.myarchive.org;
>>>
>>> But we have something like this:
>>> AppConfig[:frontend_proxy_url] = proc { "https://staff.myarchive.org; }
>>> AppConfig[:public_proxy_url] = proc { "https://public.myarchive.org; }
>>> with the URL wrapped in proc { }. So try both and see if it helps. If
>>> the proc { } thing works then the documentation might need to be
>>> updated.
>>>
>>> On Fri, Aug 30, 2019 at 8:47 AM Kara Hart 
>>> wrote:
>>>
 Hi everyone,
 We just built a new server with openjdk 1.8.0_212; Apache/2.4.6; 5.7.26
 MySQL; CentOS Linux release 7.6.1810.
 I migrated the database from a 2.5.1 version and forced a full re-index
 by deleting the data directory contents. At the same time we installed
 certificates to start to serve the PUI and Staff UI over https. My Systems
 staff added the settings to the apache config file and I edited the
 config.rb file and entered the lines as suggested in the https setup
 documentation
 
 .

 I'm having a problem with the AS not keeping https on the staff side
 when you click to view or edit records.  I can search and get a list of
 result records in the AS staff UI and navigate around, but when I click on
 a record to edit or view I'm getting a requested resource is not found on
 server error.

 EX: a link to a record

 https://archivesstaff.wellesley.edu/resolve/edit?uri=/repositories/2/resources/51
 should redirect to

 https://archivesstaff.wellesley.edu/resources/51#tree::archival_object_15295
 but instead I get routed to insecure
 http://archivesstaff.wellesley.edu/resources/51/edit
 with error "Not Found The requested URL /resources/51 was not
 found on this server."
 If I change the last url to https, manually, it does render the edit
 page.

 Any idea with is going on or of a setting I'm missing somewhere?

 Thanks,

 Kara

 ~~~ Kara S. Hart
 Systems Librarian - Library & Technology Services
 -
 Wellesley College

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

>>>
>>>
>>> --
>>> Trevor Thornton

[Archivesspace_Users_Group] ArchivesSpace Update - August 2019

[Jessica Crouch]

ArchivesSpace August 2019 Update
Development

We are getting close to having a release candidate available for the work we've 
been doing on some needed infrastructure improvements for the application and 
making recording language information more standards-compliant in this area. 
The release candidate will also have some bug fixes and small feature 
enhancements. Look for an announcement in September.


Are you interested in helping make the ArchivesSpace application better for the 
community by contributing code for small bug fixes and features? Our 
Development Prioritization sub-team recently worked with the program team to 
launch a Ready for Community 
Developer status to 
make it easier to identify JIRA issues that are especially appropriate for 
community contributions. Development Prioritization sub-team leaders Lydia Tang 
and Maggie Hughes presented about it at our Annual Member Forum in Austin 
earlier this month: https://youtu.be/qK84vgmS66 . 
You can also reach out to Christine Di Bella 
(christine.dibe...@lyrasis.org) or Laney 
McGlohon (laney.mcglo...@lyrasis.org) for 
more information about how to get involved with working on these issues.

Fifth Annual Member Forum Survey and Recordings Now Available!

Thank you to all who attended the 5th Annual Member Forum at the Thompson 
Conference Center in Austin, Texas!  It was a lively event with 95 attendees 
and presentations from 21 individuals from ArchivesSpace member institutions 
and the ArchivesSpace program team.  It was also our first Annual Forum with 
attendees from our international member community! And a special thank you to 
all of you who joined us after the forum for our joint reception with 
Archive-It.


In order to make next year’s forum in Chicago even better, we hope you will 
take the time to complete our post forum 
survey.  You do not have to have 
attended the forum in Austin to complete this survey.


All recorded sessions and presentation slides are also now available on the 
ArchivesSpace 
wiki.

Community Open Call: September 18th at 2-3pm ET (11-noon PT)

Please join us for our next community open call on Zoom on September 18th at 
2-3pm ET (11-noon PT). This is an opportunity to talk informally about ideas 
you’ve had, challenges you’ve encountered, or news you’d like to share. This 
might be an especially good chance to talk about non-technical questions or 
ideas that you weren’t quite sure about posting on the Users Group listserv but 
really would like help with from us or your peers. Information on how to join 
the call can be found on the ArchivesSpace 
blog.



We have a pre-survey to help generate 
discussion topics prior to the call. Please submit your suggestions by Tuesday, 
September 17th.

Upcoming Webinar: Introducing the PBSpace Plugin

September 26th, 2-3pm ET (11-noon PT)

Visit the ArchivesSpace Blog for 
details.

Jason Corum will explore the new PBSpace plugin, available via github: 
https://github.com/WGBH-MLA/pbspace. PBCore is a data model 
for the description of audiovisual content.  The PBSpace plugin adds new 
properties and object relationships in the application so that PBCore 
structure, elements, and attributes can be better represented in ArchivesSpace. 
Jason will discuss a little about what PBCore is and who uses it, the process 
of developing the plugin, and demonstrate the plugin itself and how it can be 
used to extend description of audiovisual content in ArchivesSpace.

The WGBH Media Library and Archives developed 
PBSpace, which has been made possible in 
part by the National Endowment for the Humanities: Exploring the human 
endeavor. Development of the PBSpace plugin was part of the Association of 
Moving Image Archivists (AMIA) Conference’s Hack Day in 2018.

Presenter:

Jason Corum is a coder and artist based in Los Angeles, CA. After a 10-year 
career in online communications with organizations like the Biotechnology 
Industry Organization, the Brookings Institution, and World Food Program USA, 
Jason decided to build cool online tools rather than manage them. Through 
self-education and a backend web development course, Jason transitioned to a 
career in web development and is now a developer with the WGBH Media Library 
and Archives 
(https://www.wgbh.org/foundation/what-we-do/media-library-and-archives). At 
WGBH, Jason works on the American Archive of Public Broadcasting 
(http://americanarchive.org/), OpenVault from WGBH 
(http://openvault.wgbh.org/), Fix It + 

Re: [Archivesspace_Users_Group] Archivesspace dropping https in Staff UI

[Majewski, Steven Dennis (sdm7g)]

> On Aug 30, 2019, at 10:55 AM, Kara Hart  wrote:
> 
> I've tried these three different settings.  
> 
> AppConfig[:frontend_proxy_url] = "https://archivesstaff.wellesley.edu 
> "
> AppConfig[:public_proxy_url] = "https://archives.wellesley.edu 
> "
> 
> AppConfig[:frontend_proxy_url] = proc { "https://archivesstaff.wellesley.edu 
> " }
> AppConfig[:public_proxy_url] = proc { "https://archives.wellesley.edu 
> " }
> 
> AppConfig[:frontend_proxy_url] = proc { 
> AppConfig[:https://archivesstaff.wellesley.edu 
> ] }
> AppConfig[:public_proxy_url] = proc { 
> AppConfig[:https://archives.wellesley.edu ] }
> 
> The last broke AS launching, which makes sense.  I think the default is to 
> use AppConfig[:frontend_url]
> which is AppConfig[:frontend_url] = "http://localhost:8080 
> " by default.  
> 

The “:” indicates a symbol in Ruby, which is a special kind of string constant
https://reactive.io/tips/2009/01/11/the-difference-between-ruby-symbols-and-strings
 


And   'AppConfig[:https://archivesstaff.wellesley.edu 
] ‘ is bad Ruby syntax unless quoted like 
 'AppConfig[:"https://archivesstaff.wellesley.edu 
”] 
But it likely not something you want anyway unless you have assigned something 
to that value previously.  


> I wonder if that is it.  Because before we made this change the link to the 
> staff interface from the public interface was http://localhost:8080 
>  and never rendered.  I wonder if there's another 
> apache setting I need for localhost?
> 

You don’t really want localhost for any of the proxy URLs. 
Localhost is fine for the URLs that are used internally, for example for the 
frontend or PUI to communicate with the backend. 
Unless you have set things up for multiple frontends on different hosts to talk 
to a single backend host, all of the services are
Running on the same host, and it’s the localhost.  But “localhost” doesn’t 
export.  If you send a localhost link to the browser,
It means, in the context of the browser, the same host the browser is running 
on, not the host the other service is on. 
So the code that adds the PUI link from the staff web app doesn’t add it if the 
proxy URL points to  “localhost". 




> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> 
> On Fri, Aug 30, 2019 at 9:04 AM Trevor Thornton  > wrote:
> I think these are the settings in config.rb that make that work correctly 
> (from the documentation):
> AppConfig[:frontend_proxy_url] = "https://staff.myarchive.org 
> "
> AppConfig[:public_proxy_url] = "https://public.myarchive.org 
> "
> 
> But we have something like this:
> AppConfig[:frontend_proxy_url] = proc { "https://staff.myarchive.org 
> " }
> AppConfig[:public_proxy_url] = proc { "https://public.myarchive.org 
> " }
> with the URL wrapped in proc { }. So try both and see if it helps. If the 
> proc { } thing works then the documentation might need to be updated.
> 
> On Fri, Aug 30, 2019 at 8:47 AM Kara Hart  > wrote:
> Hi everyone, 
> We just built a new server with openjdk 1.8.0_212; Apache/2.4.6; 5.7.26 
> MySQL; CentOS Linux release 7.6.1810.
> I migrated the database from a 2.5.1 version and forced a full re-index by 
> deleting the data directory contents. At the same time we installed 
> certificates to start to serve the PUI and Staff UI over https. My Systems 
> staff added the settings to the apache config file and I edited the config.rb 
> file and entered the lines as suggested in the https setup documentation 
> .
>  
> 
> I'm having a problem with the AS not keeping https on the staff side when you 
> click to view or edit records.  I can search and get a list of result records 
> in the AS staff UI and navigate around, but when I click on a record to edit 
> or view I'm getting a requested resource is not found on server error. 
> 
> EX: a link to a record  
> https://archivesstaff.wellesley.edu/resolve/edit?uri=/repositories/2/resources/51
>  
> 
> should redirect to 
> https://archivesstaff.wellesley.edu/resources/51#tree::archival_object_15295 
> 
> but instead I get routed to insecure 
> http://archivesstaff.wellesley.edu/resources/51/edit 
> 

Re: [Archivesspace_Users_Group] Archivesspace dropping https in Staff UI

[Kara Hart]

Cont. thoughts from last email...
In fact, it looks like my System staff didn't add the redirects to the
apache config files.

If I added these lines to that config, would that possibly fix the
problem?


ServerName archivesstaff.wellesley.edu
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://archivesstaff.wellesley.edu$1 [R,L]



ServerName archives.wellesley.edu
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://archives.wellesley.edu$1 [R,L]



Thanks, Kara

~~~ Kara S. Hart

Systems Librarian - Library & Technology Services - Wellesley College



On Fri, Aug 30, 2019 at 10:55 AM Kara Hart  wrote:

> I've tried these three different settings.
>
> AppConfig[:frontend_proxy_url] = "https://archivesstaff.wellesley.edu;
> AppConfig[:public_proxy_url] = "https://archives.wellesley.edu;
>
> AppConfig[:frontend_proxy_url] = proc { "
> https://archivesstaff.wellesley.edu; }
> AppConfig[:public_proxy_url] = proc { "https://archives.wellesley.edu; }
>
> AppConfig[:frontend_proxy_url] = proc { AppConfig[:
> https://archivesstaff.wellesley.edu] }
> AppConfig[:public_proxy_url] = proc { AppConfig[:
> https://archives.wellesley.edu] }
>
> The last broke AS launching, which makes sense.  I think the default is to
> use AppConfig[:frontend_url]
> which is AppConfig[:frontend_url] = "http://localhost:8080; by default.
>
> I wonder if that is it.  Because before we made this change the link to
> the staff interface from the public interface was http://localhost:8080
> and never rendered.  I wonder if there's another apache setting I need for
> localhost?
>
>
>
> ~~~ Kara S. Hart
> Systems Librarian - Library & Technology Services
> -
> Wellesley College
>
>
> On Fri, Aug 30, 2019 at 9:04 AM Trevor Thornton  wrote:
>
>> I think these are the settings in config.rb that make that work correctly
>> (from the documentation):
>> AppConfig[:frontend_proxy_url] = "https://staff.myarchive.org;
>> AppConfig[:public_proxy_url] = "https://public.myarchive.org;
>>
>> But we have something like this:
>> AppConfig[:frontend_proxy_url] = proc { "https://staff.myarchive.org; }
>> AppConfig[:public_proxy_url] = proc { "https://public.myarchive.org; }
>> with the URL wrapped in proc { }. So try both and see if it helps. If
>> the proc { } thing works then the documentation might need to be updated.
>>
>> On Fri, Aug 30, 2019 at 8:47 AM Kara Hart  wrote:
>>
>>> Hi everyone,
>>> We just built a new server with openjdk 1.8.0_212; Apache/2.4.6; 5.7.26
>>> MySQL; CentOS Linux release 7.6.1810.
>>> I migrated the database from a 2.5.1 version and forced a full re-index
>>> by deleting the data directory contents. At the same time we installed
>>> certificates to start to serve the PUI and Staff UI over https. My Systems
>>> staff added the settings to the apache config file and I edited the
>>> config.rb file and entered the lines as suggested in the https setup
>>> documentation
>>> 
>>> .
>>>
>>> I'm having a problem with the AS not keeping https on the staff side
>>> when you click to view or edit records.  I can search and get a list of
>>> result records in the AS staff UI and navigate around, but when I click on
>>> a record to edit or view I'm getting a requested resource is not found on
>>> server error.
>>>
>>> EX: a link to a record
>>>
>>> https://archivesstaff.wellesley.edu/resolve/edit?uri=/repositories/2/resources/51
>>> should redirect to
>>>
>>> https://archivesstaff.wellesley.edu/resources/51#tree::archival_object_15295
>>> but instead I get routed to insecure
>>> http://archivesstaff.wellesley.edu/resources/51/edit
>>> with error "Not Found The requested URL /resources/51 was not found
>>> on this server."
>>> If I change the last url to https, manually, it does render the edit
>>> page.
>>>
>>> Any idea with is going on or of a setting I'm missing somewhere?
>>>
>>> Thanks,
>>>
>>> Kara
>>>
>>> ~~~ Kara S. Hart
>>> Systems Librarian - Library & Technology Services
>>> -
>>> Wellesley College
>>>
>>> ___
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group@lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>
>>
>>
>> --
>> Trevor Thornton
>> Applications Developer, Digital Library Initiatives
>> North Carolina State University Libraries
>> ___
>> 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

[Archivesspace_Users_Group] Proc {} in config.rb. [was: Archivesspace dropping https in Staff UI]

[Majewski, Steven Dennis (sdm7g)]

No proc {} wrapper needed for a literal string. 

The proc is creating a code block or procedure that will be run to get the 
value, and it’s purpose is to defer assignment, 
Typically where the AppConfig assignment is based on another value from 
AppConfig. 
That way, if a variable is changed from it’s default in config.rb, the 
dependent variable will also be changed. 

For example, from config-defaults.rb:  

AppConfig[:db_max_connections] = proc { 20 + (AppConfig[:indexer_thread_count] 
* 2) }


I have used proc {} wrapped around assignments in my config.rb , but I’m not 
sure that usage is even necessary:
Now that I think about it, it may only be needed in config-defaults to pick up 
changes added to config.rb . 
Once config.rb is being executed, there is already an AppConfig created with 
those defaults, and as long as 
your additions to config.rb are sequential, I don’t think the proc matters 
most* of the time. 


(*)  ‘most of the time’ : 

Where I have needed it is in adding: 

AppConfig[:hostname] = { Socket.gethostname }
# … 
AppConfig[:public_proxy_url] = proc { "http://#{AppConfig[:hostname]}:8081” }

To use actual host names instead of localhost for proxy urls.
But I believe that is mostly needed to defer execution until initialization has 
imported Socket module,
Because elsewhere I also assign AppConfig[:environment] to either :production 
or :development 
And use that in conditionals within my config.rb . 
( if :production, then it’s using assigned VHOST names and https: in those 
proxy settings instead of AppConfig[:hostname] ) 


So I’m thinking I was under the influence of some fuzzy thinking about the 
initialization process when I wrote my config.rb code. 
It all works as is, but now that I try to reason about it, it’s a bit off! 

— Steve.



> On Aug 30, 2019, at 9:03 AM, Trevor Thornton  wrote:
> 
> I think these are the settings in config.rb that make that work correctly 
> (from the documentation):
> AppConfig[:frontend_proxy_url] = "https://staff.myarchive.org 
> "
> AppConfig[:public_proxy_url] = "https://public.myarchive.org 
> "
> 
> But we have something like this:
> AppConfig[:frontend_proxy_url] = proc { "https://staff.myarchive.org 
> " }
> AppConfig[:public_proxy_url] = proc { "https://public.myarchive.org 
> " }
> with the URL wrapped in proc { }. So try both and see if it helps. If the 
> proc { } thing works then the documentation might need to be updated.
> 
> On Fri, Aug 30, 2019 at 8:47 AM Kara Hart  > wrote:
> Hi everyone, 
> We just built a new server with openjdk 1.8.0_212; Apache/2.4.6; 5.7.26 
> MySQL; CentOS Linux release 7.6.1810.
> I migrated the database from a 2.5.1 version and forced a full re-index by 
> deleting the data directory contents. At the same time we installed 
> certificates to start to serve the PUI and Staff UI over https. My Systems 
> staff added the settings to the apache config file and I edited the config.rb 
> file and entered the lines as suggested in the https setup documentation 
> .
>  
> 
> I'm having a problem with the AS not keeping https on the staff side when you 
> click to view or edit records.  I can search and get a list of result records 
> in the AS staff UI and navigate around, but when I click on a record to edit 
> or view I'm getting a requested resource is not found on server error. 
> 
> EX: a link to a record  
> https://archivesstaff.wellesley.edu/resolve/edit?uri=/repositories/2/resources/51
>  
> 
> should redirect to 
> https://archivesstaff.wellesley.edu/resources/51#tree::archival_object_15295 
> 
> but instead I get routed to insecure 
> http://archivesstaff.wellesley.edu/resources/51/edit 
> 
> with error "Not Found The requested URL /resources/51 was not found on 
> this server."
> If I change the last url to https, manually, it does render the edit page. 
> 
> Any idea with is going on or of a setting I'm missing somewhere? 
> Thanks, 
> 
> Kara
> 
> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
> 
> 
> -- 
> Trevor Thornton
> Applications Developer, Digital Library Initiatives
> North Carolina State University Libraries
> 

Re: [Archivesspace_Users_Group] Archivesspace dropping https in Staff UI

[Trevor Thornton]

I think these are the settings in config.rb that make that work correctly
(from the documentation):
AppConfig[:frontend_proxy_url] = "https://staff.myarchive.org;
AppConfig[:public_proxy_url] = "https://public.myarchive.org;

But we have something like this:
AppConfig[:frontend_proxy_url] = proc { "https://staff.myarchive.org; }
AppConfig[:public_proxy_url] = proc { "https://public.myarchive.org; }
with the URL wrapped in proc { }. So try both and see if it helps. If the proc
{ } thing works then the documentation might need to be updated.

On Fri, Aug 30, 2019 at 8:47 AM Kara Hart  wrote:

> Hi everyone,
> We just built a new server with openjdk 1.8.0_212; Apache/2.4.6; 5.7.26
> MySQL; CentOS Linux release 7.6.1810.
> I migrated the database from a 2.5.1 version and forced a full re-index by
> deleting the data directory contents. At the same time we installed
> certificates to start to serve the PUI and Staff UI over https. My Systems
> staff added the settings to the apache config file and I edited the
> config.rb file and entered the lines as suggested in the https setup
> documentation
> 
> .
>
> I'm having a problem with the AS not keeping https on the staff side when
> you click to view or edit records.  I can search and get a list of result
> records in the AS staff UI and navigate around, but when I click on a
> record to edit or view I'm getting a requested resource is not found on
> server error.
>
> EX: a link to a record
>
> https://archivesstaff.wellesley.edu/resolve/edit?uri=/repositories/2/resources/51
> should redirect to
>
> https://archivesstaff.wellesley.edu/resources/51#tree::archival_object_15295
> but instead I get routed to insecure
> http://archivesstaff.wellesley.edu/resources/51/edit
> with error "Not Found The requested URL /resources/51 was not found
> on this server."
> If I change the last url to https, manually, it does render the edit page.
>
> Any idea with is going on or of a setting I'm missing somewhere?
>
> Thanks,
>
> Kara
>
> ~~~ Kara S. Hart
> Systems Librarian - Library & Technology Services
> -
> Wellesley College
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group