Re: [Archivesspace_Users_Group] Google Analytics/Google Tags

2023-05-22 Thread Philip Webster
Hi,
We use the aspace_analytics plugin from Dartmouth, and this makes things very 
simple - there's just a single file in the plugin directory that you paste your 
Google Analytics snippet into.

Regards,

Philip Webster


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Gadsby, 
Eric T. 
Sent: Monday, May 22, 2023 10:20:39 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Google Analytics/Google Tags


Dear Friends,



Good evening! I need to add Google Analytics/Google Tags to our new 
ArchivesSpace install. I have a snippet of Java Script our web developer 
provided me but I can’t for the life of me remember what file to add it to and 
or where?  Any help would be apricated. Thanks in advance!





[Towson University logo]<http://www.towson.edu/>

Eric T. Gadsby

Pronouns: he/him/his

IT Operations Specialist  |  Albert S. Cook Library

—

P: 410-704-3340
egad...@towson.edu<mailto:egad...@towson.edu>  |  
libraries.towson.edu<http://www.towson.edu/https:/libraries.towson.edu>
 —



Confidentiality Notice: This message may contain information that is 
confidential, privileged, proprietary, or otherwise legally exempt from 
disclosure. If you are not the intended recipient, you are notified that you 
are not authorized to read, print, copy or disseminate this message, any part 
of it, or any attachments. If this message has been sent to you in error, 
please notify the sender by replying to this transmission, or by calling Albert 
S. Cook Library at 410-704-3340 .




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


Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2023-03-28 Thread Philip Webster
Hi,

Ran into this yesterday, and I ran the SQL UPDATE query – I got a report of 4 
rows affected, but now our AS instance won’t start up due to initialisation 
errors. We are getting the same error as before.

 

Here is the console interaction for SQL:

mysql> UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Query OK, 4 rows affected (0.01 sec)

Rows matched: 4  Changed: 4  Warnings: 0

 

Here is the stack trace (first few lines):

Mar 28, 2023 12:00:08 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log

WARNING: ERROR: initialization failed

org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: 
HOUR_OF_DAY: 1 -> 2

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89)

   from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73)

from 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85)

from 
com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:947)

from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)

from 
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)

from 
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.timestamp_convert(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from org.jruby.RubyMethod.call(org/jruby/RubyMethod.java:123)

from 
org.jruby.RubyMethod$INVOKER$i$call.call(org/jruby/RubyMethod$INVOKER$i$call.gen)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther9:call(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.process_result_set(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1809)

 

This is affecting a production service, so I may have to raise a technical 
support request if there isn’t a community solution.

 

Regards,

 

Philip Webster

The University of Sheffield

 

 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 27 March 2023 09:07
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

 

A reminder to anyone in Europe, whose clocks changed this weekend, to check 
your ArchivesSpace system. If everything but the home page isn't working, try 
the fix below...

 

Andrew.

 

 

On 12/03/2023 19:57, Blake Carver wrote:

 

It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see

DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

 

Try this and restart, that'll probably do the trick. 

 

UPDATE user set user_mtime = NOW(), system_mtime=NOW();

 

 

 

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


[Archivesspace_Users_Group] "Connecting to the database failed. Retrying..." message in archivesspace.out log

2023-03-16 Thread Philip Webster
Hi,

 

I occasionally see this in the archivesspace.out log:

I, [2023-03-16T04:53:02.624812 #97628]  INFO -- : Thread-51904: Connecting
to the database failed.  Retrying...

 

Does this refer to the MySQL connection, or it this related to the Solr
index? What typically causes this?

 

Generally, it is always fixable by just restarting ArchivesSpace, and no
action is needed on MySQL/Solr.

 

Regards,

 

Philip Webster

The University of Sheffield

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


Re: [Archivesspace_Users_Group] ArchivesSpace backups on 3.2 failing

2023-01-12 Thread Philip Webster
Hi Scott, what was the solution for this in the end? We’ve just upgraded to
3.2.0 at Sheffield and we’re seeing the same thing.

 

Regards,

 

Phil

 

 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org
 On Behalf Of
RENTON Scott
Sent: 24 May 2022 17:31
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace backups on 3.2
failing

 

Thanks Andrew. Yeah, here it is (it's just the default solrconfig.xml from
archivesspace)

 

  

 

Cheers

Scott

 

==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

  _  

From: archivesspace_users_group-boun...@lyralists.lyrasis.org

mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> > on behalf
of Andrew Morrison mailto:andrew.morri...@bodleian.ox.ac.uk> >
Sent: 24 May 2022 16:56
To: archivesspace_users_group@lyralists.lyrasis.org

mailto:archivesspace_users_group@lyralists.lyrasis.org> >
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace backups on 3.2
failing 

 

This email was sent to you by someone outside the University. 

You should only click on links or attachments if you are certain that the
email is genuine and the content is safe.

Does your external Solr's "archivesspace" core define a requestHandler whose
class is "solr.ReplicationHandler" in its solrconfig.xml? Is the name
"/replication"?

 

Andrew.

 

 

On 24/05/2022 16:42, RENTON Scott wrote:

Hi folks

 

I upgraded an instance to v.3.2.0 on Friday, but notice that backups are
failing (to do with the new external SOLR?). This is using 

 

/apps/archivesspace/scripts/backup.sh --mysqldump --output
${BACKUP_DIR}/archivesspace_backup_$DATE.zip

 

as normal. Has the script changed substantially? We were on 2.8.1
previously.

 

Error looks like this:

Loading ArchivesSpace configuration file from path:
/apps/archivesspace/config/config.rb

WARNING: The parameter 'pui_email_delivery_method' was already set

WARNING: The parameter 'pui_email_perform_deliveries' was already set

WARNING: The parameter 'pui_email_raise_delivery_errors' was already set

Loading ArchivesSpace configuration file from path:
/apps/archivesspace/config/config.rb

WARNING: The parameter 'pui_email_delivery_method' was already set

WARNING: The parameter 'pui_email_perform_deliveries' was already set

WARNING: The parameter 'pui_email_raise_delivery_errors' was already set

2022-05-24 14:32:48 +0100: Writing backup to
/apps/backups/archivesspace_backup_220524_143245.zip

ERROR: Solr snapshot failed (Solr snapshot failed: Problem when getting
snapshot details: 





Error 404 Not Found



HTTP ERROR 404 Not Found



URI:/replication

STATUS:404

MESSAGE:Not Found

SERVLET:-



 

 

Otherwise the SOLR seems to be working fine, so I'm assuming my config is
ok:

 

AppConfig[:solr_url] = "http://localhost:8983/solr/archivesspace";

AppConfig[:solr_verify_checksums] = false

AppConfig[:data_directory] =
File.join("/apps/solr/server/solr/archivesspace/data")





 

I did wonder if it was the location of the data_directory that was the
issue- it had been away from the solr core, but even after repointing that
(above), I get the above error.

 

Cheers

Scott

 

 

==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland,
with registration number SC005336. Is e buidheann carthannais a th’ ann an
Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336. 



___
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] New user creation issue "Must be one of: ISAAR (CPF) and NCA Rules"

2022-12-14 Thread Philip Webster
Thanks – this was the solution.

 

Ideally, it would be nice if the drop-down entry could be hidden in some way 
without breaking the back-end  functionality.

 

Regards,

 

Phil

 

 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 22 November 2022 12:15
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] New user creation issue "Must be one 
of: ISAAR (CPF) and NCA Rules"

 

In the staff interface, go to System > Manage Controlled Value Lists. Then 
select "Name Rule (name_rule)" from the List Name drop-down. If that list 
doesn't have a value of "local", or that value has been suppressed, that could 
be the cause of your problem.

The issue is that creating system users also creates an (unpublished) agent 
record. So, if you've suppressed local rules for the naming of persons in your 
metadata, it'll won't be able to create the agent, so it won't be able to 
create the user either.

Andrew.

 

On 22/11/2022 11:22, Philip Webster wrote:

Hi,

 

I’m the admin for ArchivesSpace at the University of Sheffield, in the UK. 
We’ve had ArchivesSpace since version 2.7, and we currently run 2.8.1 with 
plans to move to 3.2.0 within the next month.

 

During our initial setup and launch, a number of user accounts were created for 
our permanent archival, metadata and technical staff. Since then we have had 
two new members of staff who qualified for ArchivesSpace accounts on our local 
system.

 

Unfortunately, it hasn’t been possible to create these accounts due to an issue 
in the staff user interface. I have populated the fields on the user form, and 
this is always done using the ‘admin’ account. When the form is submitted, the 
response is as follows:

 

Invalid value 'local'. Must be one of 'ISAAR (CPF) and NCA Rules'

User not created

 

Looking at the logs, I see that the frontend is sending the following data to 
the server (response lines are also shown, sensitive information redacted):

I, [2022-11-17T17:45:11.671710 #98122]  INFO -- : Started POST "/users" for 
REDACTED-IP at 2022-11-17 17:45:11 +

I, [2022-11-17T17:45:11.822783 #98122]  INFO -- : Processing by 
UsersController#create as HTML

I, [2022-11-17T17:45:11.823274 #98122]  INFO -- :   Parameters: {"utf8"=>"✓", 
"authenticity_token"=>"REDACTED", "user"=>{"lock_version"=>"", 
"username"=>"testuser_t", "name"=>"testuser", "email"=>du...@sheffield.ac.uk 
<mailto:du...@sheffield.ac.uk> , "first_name"=>"test", "last_name"=>"user", 
"telephone"=>"", "title"=>"", "department"=>"Library", 
"additional_contact"=>"", "password"=>"[FILTERED]", 
"confirm_password"=>"[FILTERED]", "is_active_user"=>"1"}}

D, [2022-11-17T17:45:12.171371 #98122] DEBUG -- : Thread-3254: POST 
/users?repo_id=2&password=[FILTERED] [session: #"admin", :login_time=>2022-11-17 17:15:54 +, 
:expirable=>true}, @system_mtime=2022-11-17 17:44:46 UTC, @id="REDACTED">]

D, [2022-11-17T17:45:12.185350 #98122] DEBUG -- : Thread-3254: Post-processed 
params: {"password"=>"[FILTERED]", "user"=>#"testuser_t", "name"=>"testuser", "email"=>du...@sheffield.ac.uk 
<mailto:du...@sheffield.ac.uk> , "first_name"=>"test", "last_name"=>"user", 
"department"=>"Library", "is_active_user"=>true, "is_admin"=>false, 
"jsonmodel_type"=>"user", "groups"=>[]}>}

D, [2022-11-17T17:45:12.252354 #98122] DEBUG -- : Thread-3254: Responded with 
[400, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"424"}, 
["{\"error\":{\"rules\":[\"Invalid value 'local'.  Must be one of: ISAAR (CPF) 
and NCA Rules\"]},\"warning\":{},\"invalid_object\":\"#\\\  "testuser\\\", \\\ 
 "source\\\"=>\\\"local\\\", \\\ 
 "rules\\\"=>\\\"local\\\", \\\ 
 "name_order\\\"=>\\\"direct\\\", \\\ 
 
"sort_name_auto_generate\\\"=>true, \\\  
"use_dates\\\"=>[], \\\  
"authorized\\\"=>true... in 83ms

I, [2022-11-17T17:45:12.307673 #98122]  INFO -- :   Rendering 
users/new.html.erb within layouts/application

I, [2022-11-17T17:45:12.3835

[Archivesspace_Users_Group] New user creation issue "Must be one of: ISAAR (CPF) and NCA Rules"

2022-11-22 Thread Philip Webster
T17:45:13.139762 #98122]  INFO -- :   Rendered 
shared/_templates.html.erb (24.2ms)

I, [2022-11-17T17:45:13.167381 #98122]  INFO -- : Completed 200 OK in 1343ms 
(Views: 857.1ms)

 

 

I’ve tested this on a dev server with a backup of our production database, with 
the ArchivesSpace code replaced with stock builds of 2.8.1 and 3.2.0 from 
GitHub, using a near-default config that only had the changes necessary to 
allow connection to MySQL and to specify the PUI/SUI URLs. In these cases the 
problem still occurs.

 

I have also tried dropping the entire database and created a fresh set of 
tables (without data) using the database setup script. This seems to work. Thus 
I conclude that something in the database affects the operation of the user 
creation component, and this is independent from the config file or code.

 

The key issue is that a value of ‘local’ is being passed, and the error message 
is telling me that it should instead "Must be one of: ISAAR (CPF) and NCA 
Rules”.

 

What do I need to do to get rid of the ‘local’ value that is being passed and 
to get the correct value instead?

 

Regards,

 

Philip Webster

The University Library

University of Sheffield

 

 

 

 

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


Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)

2021-01-18 Thread Philip Webster
Hi,

Java -version on the affected server gives the following:

openjdk version "11.0.9.1" 2020-11-04

OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04)

OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed
mode, sharing)

 

Regards,

 

Phil

 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org
 On Behalf Of
Andrew Morrison
Sent: 15 January 2021 14:51
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI
(2.8.1)

 

Which version of Java are you running?

See
http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-Fe
bruary/007388.html

Andrew.

 

On 13/01/2021 12:56, philip.webs...@sheffield.ac.uk
<mailto:philip.webs...@sheffield.ac.uk>  wrote:

Hi,

We're currently in the process of deploying ArchivesSpace 2.8.1 to our
production server following a lengthy period of testing and development on
some other servers. Strangely, the public user interface is failing to load
due to a Ruby dependency not being pulled in when the service starts up. The
dependency is SASSC, which is present in the gems folder within the
ArchivesSpace 2.8.1 installation.

 

An error message appears in the logs suggesting that SASSC isn't being
imported due to it not having native extensions built, and in turn that
causes a 500 error to be visible in the browser together with a stack trace
showing the root cause to be the missing library. I tried building the
extension using the native Ruby tools in our Linux distribution and found
that had no effect. After some lengthy investigation it turned out that the
development and test servers do not even have the native Ruby packages
installed, and that everything runs entirely through jRuby. That being the
case, I have no idea how to solve the issue with this dependency.

 

None of this is mentioned in the documentation, so I'm at a loss as to what
to do next.

 

Does anyone have any suggestions? 

 

Thanks, 

 

Philip Webster 

The University of Sheffield 

 





___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
<mailto: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] Ruby SASSC issue affecting PUI (2.8.1)

2021-01-13 Thread philip . webster
Hi,

We're currently in the process of deploying ArchivesSpace 2.8.1 to our
production server following a lengthy period of testing and development on
some other servers. Strangely, the public user interface is failing to load
due to a Ruby dependency not being pulled in when the service starts up. The
dependency is SASSC, which is present in the gems folder within the
ArchivesSpace 2.8.1 installation.

 

An error message appears in the logs suggesting that SASSC isn't being
imported due to it not having native extensions built, and in turn that
causes a 500 error to be visible in the browser together with a stack trace
showing the root cause to be the missing library. I tried building the
extension using the native Ruby tools in our Linux distribution and found
that had no effect. After some lengthy investigation it turned out that the
development and test servers do not even have the native Ruby packages
installed, and that everything runs entirely through jRuby. That being the
case, I have no idea how to solve the issue with this dependency.

 

None of this is mentioned in the documentation, so I'm at a loss as to what
to do next.

 

Does anyone have any suggestions? 

 

Thanks, 

 

Philip Webster 

The University of Sheffield 

 

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


[Archivesspace_Users_Group] Loading long CSV files for accessions in ArchivesSpace

2020-10-19 Thread philip . webster
Hi,

One thing we have noticed when attempting to batch load accessions using CSV
import capability in ArchivesSpace is that there appears to be some sort of
limit that prevents us from loading large numbers of items.

I could think of several reasons why this may be the case.

1.  There may be a hard-coded limit on the number of rows that can be
processed in a single background process.
2.  There may be a relationship between the amount of memory allocated
to ArchivesSpace and the number of rows that can be processed.
3.  There may be a limited amount of time the background process can run
for.

 

Our current workaround is to split the accessions import CSV into multiple
files and load them in sequence.

Does anyone on the mailing list know what could be causing the batch process
stop before finishing an entire CSV file?

 

Regards,

Philip Webster 

The University of Sheffield 

 

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


[Archivesspace_Users_Group] Aspace-Oauth SAML configuration

2020-10-06 Thread philip . webster
Hi,

I'm trying to set up the Aspace-Oauth plugin on ArchivesSpace 2.8.0 to
enable SAML logins via our institutional IDP. So far, I've managed to get
the plugin linked to our dev IDP and configured to download the SAML
metadata. Our IT department has requested that all security assertions are
at least signed, and preferably encrypted.

 

I've also generated a private key and certificate using the commands listed
in the README.md file in the github repo
(https://github.com/lyrasis/aspace-oauth).

openssl genrsa -out rsaprivkey.pem 2048

openssl req -new -x509 -key rsaprivkey.pem -out rsacert.pem

 

The documentation is quite sparse, and doesn't really explain what to do
next. The config sample given in the README.md has the following parameters
defined in the example:

# OPTIONAL: for encrypted assertions

  :certificate=> "PUBLIC CERT",

  :private_key=> "PRIVATE KEY",

 

What are the expected values for "PUBLIC CERT" and "PRIVATE KEY"? Should
these be the paths of the rsaprivkey.pem and rsacert.pem files, or am I
expected to paste the ASCII contents of the .pem files straight into the
config file?

 

Once this is set up, I also have to define the name identifier format. The
default setting in the config is 

"urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress", and further down
there is 

email: ["urn:oid:0.9.2342.19200300.100.1.3"]. I do want to populate the
email field in the user records in ArchiveSpace's database, but at my
institution we prefer to use eduPersonPrincipalName
(urn:oid:1.3.6.1.4.1.5923.1.1.1.6) as an identifier instead of email
address.

 

Hopefully, ArchivesSpace Oauth will support this, and I assume I can just
substitute "eduPersonPrincipalName" in place of "emailAddress" in the config
file.

 

The README.md file also refers to some 'project documentation', but I
haven't been able to find this anywhere on the community documentation. Is
there any other documentation other than the README, and if so, where is it?

 

Once this is all set up, I'll have to send some metadata to our IT
department. I'm hoping that there is an endpoint somewhere that I can point
a browser at and get the generated metadata for the service, so I can just
pass that on. Again, it's not clear if such a thing exists - or how I'd go
about accessing it.

 

 

If anyone has any advice for the issues described above, I'd be very
grateful to hear it!

 

Regards,

 

Philip Webster

The University Library

University of Sheffield

 

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