Re: [Archivesspace_Users_Group] EAD import extents mapping

[Rees, John (NIH/NLM) [E]]

Thanks Mark. Luckily we only use one  statement and the syntax is 
pretty uniform across our corpus.

Today I discovered a 2nd  sans  will also import nicely into 
a Physical Description Note. This note exports as a vanilla  but your 
approach produces more specific and parsable EAD for down the road.

And yes, I've been tracking the silent label drops esp. since our external 
public access application often depends on them.

John


From: Custer, Mark [mailto:mark.cus...@yale.edu]
Sent: Friday, June 22, 2018 8:59 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping

John,

And it case it helps, here's the admittedly hacky way that I've handled this in 
the past, only focusing on splitting out those linear footage statements since 
that's what we had to deal with:












   

















I should note, though, that our incoming EAD files would only have a single 
extent statement to begin with, so I wouldn't use this without inspecting 
another EAD corpus before running it there.  But for the example that you 
originally provided, it should do the trick.  Just be careful if those 
statements aren't uniform in your corpus, since the above template really only 
expects physdesc elements with a single extent child.

Mark



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Custer, Mark
Sent: Friday, 22 June, 2018 8:50 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping

John,

What I think that you'd want to do in this case is to modify the EAD so that it 
looks like the following:


15.0 linear_feet
(36 boxes + oversize folder)


Two important points about this:


  1.  The ASpace EAD importer uses the database values for controlled value 
fields, which is why I've changed linear feet to "linear_feet"  ("linear_feet" 
is one of the database values available in ASpace by default, but if that's not 
the value that matches your YML translation, you might want to use another 
one).  The ASpace EAD exporter, on the other hand, will use the YML translation 
when exporting the EAD, so you'd wind up with "linear feet" in the export, or 
whatever else is specified in the YML file that's being employed by your 
application.
  2.  Whatever you put into a second extent statement will be mapped to the 
Container Summary field in ArchivesSpace.

This is essentially following the AT model for importing EAD physdesc elements. 
 I wish, instead, that ASpace would only add extent values based on the 
availability of the extent/@unit attribute in EAD 2002.   That would make 
things a lot less dicey than trying to  parse the text field of an extent 
element during import time, but it would require more EAD manipulation for a 
lot of folks before importing that data since the @unit attribute isn't heavily 
used.

Mark

p.s.   the physdesc/@label attribute, however, does NOT get mapped at all by 
ASpace.  Instead, it's dropped silently during the import process.  That used 
to be the case, at least.  I haven't checked in a while to see if that behavior 
has been changed, but in general label attributes and head elements will 
usually map to the ASpace label field.

p.p.s. I've never tested to see what happens if you have a third sibling extent 
statement (to see if those get dropped or appended to container summary).  But 
I have tested using dimensions and/or physfacet within the same grouping, and 
those are imported as expected.




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Rees, John (NIH/NLM) [E]
Sent: Thursday, 21 June, 2018 3:43 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] EAD import extents mapping

Using the background job importer, I'm trying to import extent data from EAD 
2002 schema XML, specifically the other extent data we record in parenthesis 
like  15.0 linear feet 
(36 boxes + oversize folder) 

I'd like these parenthetical statements to map to the Container Summary field. 
According to the EAD import mapper 
http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx

Re: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete

[Christine Di Bella]

Hi Daniel,

I'm going to put a support ticket in for you on this. (You'll see another 
message about that directly to you in a minute.) It'd be great if you posted 
the answer back to the list when it's resolved.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Daniel L 
Thacker
Sent: Friday, June 22, 2018 12:02 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] That ID is already in use problem and not 
being able to delete


Hello,



We imported a collection on Monday and it went through fine.  Then we had an 
error where we could not merge collections (it was an "db_error" {"Database 
integrity constraint conflict: Java: 
ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait 
timeout exceeded: try restarting transaction"). We tired to back up the 
database straight from MySQL and took 30 minutes instead of the usual 10 
seconds. Then we decided to roll back to a previous back-up, which worked.  The 
collection I put in on Monday was gone.  Since we went to the back-up I had to 
re-import the collection I put in on Monday.  The collection did not go through 
this time and got an "id_0 : That ID is already in use" error.  We cleared the 
indexes in the data folder and restored the backup again but the problem 
continues to exist.



I have attached the part of the error log that corresponds with our problem.



Thanks,



Daniel Thacker

Digital Archivist

James C. Jernigan Library

Texas A&M University-Kingsville

MSC 197

700 University Blvd

Kingsville, TX  78363-8202

361-593-4154
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Re-ordering plugins

[Paul Sutherland]

Hi all,

I have checked Awesome ArchivesSpace and can't see anything that looks like
this. Please let me know if I'm missing it.

I am wondering if anyone has created plugins for:

   - bulk re-ordering records at the same level and with the same parent
   (e.g. children of a series, either alphabetically or chronologically by
   begin date);
   - inserting new records as adjacent siblings of a currently selected
   record (a functionality that Archivists' Toolkit had)

Since moving from Archivists' Toolkit, it has become difficult to deal with
very large series that are not already arranged before entry, as all new
records go to the end of their level. Plugins for these operations would
help greatly with daily entry.

Thank you for any assistance,
Paul

-- 
*Paul Sutherland* (he/his)
Archivist
Center for Native American and Indigenous Research
American Philosophical Society
105 S. 5th Street, 2nd Floor
Philadelphia, PA 19406
215-440-3408
amphilsoc.org/library/CNAIR

Browse our new Indigenous Subject Guide

and read our latest blog posts

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

[Archivesspace_Users_Group] That ID is already in use problem and not being able to delete

[Daniel L Thacker]

Hello,


We imported a collection on Monday and it went through fine.  Then we had an 
error where we could not merge collections (it was an "db_error" {"Database 
integrity constraint conflict: Java: 
ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait 
timeout exceeded: try restarting transaction"). We tired to back up the 
database straight from MySQL and took 30 minutes instead of the usual 10 
seconds. Then we decided to roll back to a previous back-up, which worked.  The 
collection I put in on Monday was gone.  Since we went to the back-up I had to 
re-import the collection I put in on Monday.  The collection did not go through 
this time and got an "id_0 : That ID is already in use" error.  We cleared the 
indexes in the data folder and restored the backup again but the problem 
continues to exist.


I have attached the part of the error log that corresponds with our problem.


Thanks,


Daniel Thacker

Digital Archivist

James C. Jernigan Library

Texas A&M University-Kingsville

MSC 197

700 University Blvd

Kingsville, TX  78363-8202

361-593-4154
D, [2018-06-22T09:05:34.598000 #3328] DEBUG -- : Thread-6848: Post-processed 
params: {:id=>63121, :repo_id=>2, :resolve=>["subjects", "related_resources", 
"linked_agents", "revision_statements", "container_locations", 
"digital_object", "classifications", "related_agents", "resource", "parent", 
"creator", "linked_instances", "linked_records", "related_accessions", 
"linked_events", "linked_events::linked_records", 
"linked_events::linked_agents", "top_container", "container_profile", 
"location_profile", "owner_repo"]}
D, [2018-06-22T09:05:34.598000 #3328] DEBUG -- : Thread-6876: Responded with 
[500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"34"}, ["{\"error\":\"key not 
found: :63121\"}\n"]]... in 32ms
I, [2018-06-22T09:05:34.598000 #3328]  INFO -- : Completed 200 OK in 32ms 
(Views: 0.6ms)
D, [2018-06-22T09:05:34.613000 #3328] DEBUG -- : Thread-6848: Responded with 
[404, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"37"}, 
["{\"error\":\"ArchivalObject not found\"}\n"]]... in 16ms
I, [2018-06-22T09:05:34.613000 #3328]  INFO -- :   Rendering 404.html.erb
I, [2018-06-22T09:05:34.613000 #3328]  INFO -- :   Rendered 404.html.erb (0.0ms)
I, [2018-06-22T09:05:34.629000 #3328]  INFO -- : Completed 200 OK in 47ms 
(Views: 9.8ms)
I, [2018-06-22T09:05:34.832000 #3328]  INFO -- : Thread-6858: Retrying 
transaction after retriable exception 
(Java::ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock 
wait timeout exceeded; try restarting transaction)
E, [2018-06-22T09:05:36.973000 #3328] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait 
timeout exceeded; try restarting transaction
java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor)
com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425)
com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408)
com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:951)
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973)
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909)
com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527)
com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680)
com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2483)
com.mysql.jdbc.StatementImpl.executeUpdateInternal(com/mysql/jdbc/StatementImpl.java:1552)
com.mysql.jdbc.StatementImpl.executeLargeUpdate(com/mysql/jdbc/StatementImpl.java:2607)
com.mysql.jdbc.StatementImpl.executeUpdate(com/mysql/jdbc/StatementImpl.java:1480)
java.lang.reflect.Method.invoke(java/lang/reflect/Method)




D, [2018-06-22T09:05:36.973000 #3328] DEBUG -- : Thread-6830: Responded with 
[400, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"192"}, 
["{\"error\":{\"db_error\":[\"Database integrity constraint conflict: 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait 
timeout exceeded; try restarting transaction\"]}}\n"]]... in 520658ms
I, [2018-06-22T09:05:36.988000 #3328]  INFO -- : Completed 500 Internal Server 
Error in 520876ms
F, [2018-06-22T09:05:36.988000 #3328] FATAL -- :   
F, [2018-06-22T09:05:36.988000 #3328] FATAL -- : Exception (Unknown response: 
#):
F, [2018-06-22T09:05:36.988000 #3328] FATAL -- :   
F, [2018-06-22T09:05:36.988000 #3328] FATAL -- : 
app/controllers/archival_objects_controller.rb:164:in `delete'
I, [2018-06-22T09:05:38.91 #3328]  INFO -- : Started GET "/resources" for 
10.11.141.57 at 2018-06-22 09:05:38 -0500
I, [2018-06-22T09:05:38.91 #3328]  INFO -- : Processing by 
ResourcesController#index as HTML
D, [2018-06-22T09:05:38.973000 #3328] DEBUG -- : Thread-6876: GET 
/repositories/2/se

Re: [Archivesspace_Users_Group] Finalized program for the SoCal Regional Forum - June 28

[Christine Kim]

Hi everyone,

I would like to offer a correction and clarification on the SoCal Regional 
Forum. The date of the forum is Thursday, June 28.

Registration is still open! 
https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674

Best wishes,
Christine Kim

Christine Kim
ArchivesSpace Community Engagement Coordinator
christine@lyrasis.org
800.999.8558 x4820
404.592.4820
Skype: ckim.lyrasis

From: archivesspace_member_reps-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_member_reps-boun...@lyralists.lyrasis.org] On Behalf Of 
Christine Kim
Sent: Tuesday, June 19, 2018 4:02 PM
Subject: [Archivesspace_member_reps] Finalized program for the SoCal Regional 
Forum - June 28

Hi everyone,

We are one week away from the SoCal Regional Forum! The finalized 
program
 for the SoCal Regional Forum is now available and includes information on 

 presentations, workshops, the post-forum mixer, and parking 
information.


  *   Program: A finalized program is now available: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum


  *   Afternoon activities: Selected by the community vote through 
registration, the afternoon will provide a variety of overviews in different 
formats. We will have an Introduction to ArchivesSpace workshop for those who 
choose to attend, with a group discussion on a variety of topics running in 
parallel. Following, we will have an overview of plug-ins. Last, we will have 
demonstration and discussion of the Digital Objects module. A laptop is not 
required to follow along, but is welcome if you'd like to try anything out.


  *   Lunch: A catered lunch will be provided.


  *   Post-event mixer: After the program's conclusion, we will move out to the 
Anthill Pub & Grille for an optional (and fun!) opportunity to continue our 
conversations in a more casual and personal way


  *   On-site volunteers: If you plan to attend the forum, please consider 
volunteering for special tasks throughout the day. This will not be a full day 
commitment, but rather for specific assigned segments throughout the day, such 
as notetaking or photography. Please feel free to view the opportunities and 
sign up directly on this sheet: https://goo.gl/Hc662B

Registration is still open! 
https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674

Special thanks to working group members Elvia Arroyo-Ramirez (UCI Libraries), 
Krystal Tribbett (UCI Libraries), and Margaret Hughes (UCLA) for putting 
together an incredible program.

Best wishes,
Christine Kim

Christine Kim
ArchivesSpace Community Engagement Coordinator
christine@lyrasis.org
800.999.8558 x4820
404.592.4820
Skype: ckim.lyrasis

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

[Archivesspace_Users_Group] Finding aids missing after migration

[Matthew Lawson]

We recently migrated to ArchivesSpace 2.3.2 from Archon.  Our collection
organization and container inventory tabs do not lead to any URL and the
Folders link to empty folders.  Has anyone seen this before?

Might a plausible way of addressing the situation be to re-import this data
as EAD?

-Matt Lawson
University of Iowa
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace v2.4.1 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.4.1. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.4.1.

This minor release fixes a bug introduced in 2.4.0 that affected searching by 
date in the public user interface. Thank you to Mark Custer for identifying the 
issue so that our developers could quickly address it. The release also 
contains two community contributions related to the backend, for which we thank 
James Bullen and Chris Fitzpatrick.

Information on upgrading to a new version of ArchivesSpace is available at 
http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/.
 If you have not yet upgraded to 2.4.0, we recommend going directly to 2.4.1. 
Also, if you are not currently using the public user interface, you may want to 
skip this release and wait for our next, larger release, which we expect to 
come in late July. The fixes in this release will also be included in that one.

If you have any questions or need help upgrading - or deciding whether to 
upgrade - please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] EAD import extents mapping

[Custer, Mark]

John,

And it case it helps, here's the admittedly hacky way that I've handled this in 
the past, only focusing on splitting out those linear footage statements since 
that's what we had to deal with:












   

















I should note, though, that our incoming EAD files would only have a single 
extent statement to begin with, so I wouldn't use this without inspecting 
another EAD corpus before running it there.  But for the example that you 
originally provided, it should do the trick.  Just be careful if those 
statements aren't uniform in your corpus, since the above template really only 
expects physdesc elements with a single extent child.

Mark



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Custer, Mark
Sent: Friday, 22 June, 2018 8:50 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping

John,

What I think that you'd want to do in this case is to modify the EAD so that it 
looks like the following:


15.0 linear_feet
(36 boxes + oversize folder)


Two important points about this:


  1.  The ASpace EAD importer uses the database values for controlled value 
fields, which is why I've changed linear feet to "linear_feet"  ("linear_feet" 
is one of the database values available in ASpace by default, but if that's not 
the value that matches your YML translation, you might want to use another 
one).  The ASpace EAD exporter, on the other hand, will use the YML translation 
when exporting the EAD, so you'd wind up with "linear feet" in the export, or 
whatever else is specified in the YML file that's being employed by your 
application.
  2.  Whatever you put into a second extent statement will be mapped to the 
Container Summary field in ArchivesSpace.

This is essentially following the AT model for importing EAD physdesc elements. 
 I wish, instead, that ASpace would only add extent values based on the 
availability of the extent/@unit attribute in EAD 2002.   That would make 
things a lot less dicey than trying to  parse the text field of an extent 
element during import time, but it would require more EAD manipulation for a 
lot of folks before importing that data since the @unit attribute isn't heavily 
used.

Mark

p.s.   the physdesc/@label attribute, however, does NOT get mapped at all by 
ASpace.  Instead, it's dropped silently during the import process.  That used 
to be the case, at least.  I haven't checked in a while to see if that behavior 
has been changed, but in general label attributes and head elements will 
usually map to the ASpace label field.

p.p.s. I've never tested to see what happens if you have a third sibling extent 
statement (to see if those get dropped or appended to container summary).  But 
I have tested using dimensions and/or physfacet within the same grouping, and 
those are imported as expected.




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Rees, John (NIH/NLM) [E]
Sent: Thursday, 21 June, 2018 3:43 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] EAD import extents mapping

Using the background job importer, I'm trying to import extent data from EAD 
2002 schema XML, specifically the other extent data we record in parenthesis 
like  15.0 linear feet 
(36 boxes + oversize folder) 

I'd like these parenthetical statements to map to the Container Summary field. 
According to the EAD import mapper 
http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx
 anything after a number and space that can't be parsed should import into 
Container Summary.

Is there a syntax for making this string unparsable and force this behavior? 
Currently "linear feet (36 boxes + oversize folder)" from the above imports to 
Extent @Type as a new unique value and I don't want all that data pollution.

Thanks,
John

John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510


___
Archivesspace_Users_G

Re: [Archivesspace_Users_Group] EAD import extents mapping

[Custer, Mark]

John,

What I think that you'd want to do in this case is to modify the EAD so that it 
looks like the following:


15.0 linear_feet
(36 boxes + oversize folder)


Two important points about this:


  1.  The ASpace EAD importer uses the database values for controlled value 
fields, which is why I've changed linear feet to "linear_feet"  ("linear_feet" 
is one of the database values available in ASpace by default, but if that's not 
the value that matches your YML translation, you might want to use another 
one).  The ASpace EAD exporter, on the other hand, will use the YML translation 
when exporting the EAD, so you'd wind up with "linear feet" in the export, or 
whatever else is specified in the YML file that's being employed by your 
application.
  2.  Whatever you put into a second extent statement will be mapped to the 
Container Summary field in ArchivesSpace.

This is essentially following the AT model for importing EAD physdesc elements. 
 I wish, instead, that ASpace would only add extent values based on the 
availability of the extent/@unit attribute in EAD 2002.   That would make 
things a lot less dicey than trying to  parse the text field of an extent 
element during import time, but it would require more EAD manipulation for a 
lot of folks before importing that data since the @unit attribute isn't heavily 
used.

Mark

p.s.   the physdesc/@label attribute, however, does NOT get mapped at all by 
ASpace.  Instead, it's dropped silently during the import process.  That used 
to be the case, at least.  I haven't checked in a while to see if that behavior 
has been changed, but in general label attributes and head elements will 
usually map to the ASpace label field.

p.p.s. I've never tested to see what happens if you have a third sibling extent 
statement (to see if those get dropped or appended to container summary).  But 
I have tested using dimensions and/or physfacet within the same grouping, and 
those are imported as expected.




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Rees, John (NIH/NLM) [E]
Sent: Thursday, 21 June, 2018 3:43 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] EAD import extents mapping

Using the background job importer, I'm trying to import extent data from EAD 
2002 schema XML, specifically the other extent data we record in parenthesis 
like  15.0 linear feet 
(36 boxes + oversize folder) 

I'd like these parenthetical statements to map to the Container Summary field. 
According to the EAD import mapper 
http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx
 anything after a number and space that can't be parsed should import into 
Container Summary.

Is there a syntax for making this string unparsable and force this behavior? 
Currently "linear feet (36 boxes + oversize folder)" from the above imports to 
Extent @Type as a new unique value and I don't want all that data pollution.

Thanks,
John

John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510


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

[Archivesspace_Users_Group] Consultancy opportunity: options assessment for circulation of archives and manuscripts at the Bodleian Libraries

[Susan Thomas]

Dear colleagues,

The Bodleian Libraries is seeking a consultant to conduct an options assessment 
for implementing a system of circulation for its archives and manuscripts. It 
is anticipated that this work will take place during July-Oct 2018, with the 
final version of the options assessment report due before 31 Oct 2018. If this 
work is of interest, please email me to obtain the 'Request for Quotations' 
document, which provides full background and details. The deadline for 
quotations is  9 July 2018 at 12.00 GMT.

Best wishes,

Susan


Susan Thomas
Head of Archives & Modern Manuscripts
Bodleian Library

Web: http://www.bodleian.ox.ac.uk/special-collections
Tel:+44 (0) 1865 283821
Post: Weston Library, Broad Street, Oxford, OX1 3BG


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