From jteitelbaum at pabmc.net  Wed Feb  1 10:07:52 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Wed, 1 Feb 2017 10:07:52 -0500
Subject: [Archivesspace_Users_Group] "View Published" not resolving correct
	web address
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0BEB@bmcmail2.PABMC.NET>

After doing a test migration from ARCHON to AS (1.4.2), when I am logged into the staff interface, I can edit a RESOURCE.  I have the ability then to click on VIEW PUBLISHED to see what the record would look like on the public site.  But when I click on it, I get an error stating "This page cannot be opened."  I tried it with several different records with the same result.

Now, I can open the regular public interface separately and view the record, but to have that logged-in feature not working is concerning.

It appears that it is not resolving the correct web address. When I look in the address bar when I click on View Published, it is using localhost:8081 instead of my test site, bmc-asmigrate:8081. I don't know if this is a support or a setup issue. Has this been fixed in later release (remember, this is version 1.4.2) or if it is a setup issue?


[cid:image001.jpg at 01D27C73.0CD9CF90]



Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/e9acbd94/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 31990 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/e9acbd94/attachment.jpg>

From mark.cooper at lyrasis.org  Wed Feb  1 10:30:15 2017
From: mark.cooper at lyrasis.org (Mark Cooper)
Date: Wed, 1 Feb 2017 15:30:15 +0000
Subject: [Archivesspace_Users_Group] "View Published" not resolving
 correct	web address
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0BEB@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0BEB@bmcmail2.PABMC.NET>
Message-ID: <SN2PR0801MB2287B2C665F8393AD7A77E71FE4D0@SN2PR0801MB2287.namprd08.prod.outlook.com>

Hi Jesse,


There are two settings in the config.rb file (in the config folder) that apply here:


AppConfig[:frontend_proxy_url]

For the url to your staff interface


AppConfig[:public_proxy_url]

For the url to your public interface


Update those and restart ArchivesSpace.


Best,

Mark


Mark Cooper
Technical Lead, Hosting and Support
LYRASIS
email: mark.cooper at lyrasis.org
skype: mark_c_cooper
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Teitelbaum, Jesse <jteitelbaum at pabmc.net>
Sent: Wednesday, February 1, 2017 7:07:52 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] "View Published" not resolving correct web address

After doing a test migration from ARCHON to AS (1.4.2), when I am logged into the staff interface, I can edit a RESOURCE.  I have the ability then to click on VIEW PUBLISHED to see what the record would look like on the public site.  But when I click on it, I get an error stating "This page cannot be opened."  I tried it with several different records with the same result.

Now, I can open the regular public interface separately and view the record, but to have that logged-in feature not working is concerning.

It appears that it is not resolving the correct web address. When I look in the address bar when I click on View Published, it is using localhost:8081 instead of my test site, bmc-asmigrate:8081. I don't know if this is a support or a setup issue. Has this been fixed in later release (remember, this is version 1.4.2) or if it is a setup issue?


[cid:image001.jpg at 01D27C71.65A645B0]



Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/5d7bdafc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 31990 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/5d7bdafc/attachment.jpg>

From jteitelbaum at pabmc.net  Wed Feb  1 10:40:55 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Wed, 1 Feb 2017 10:40:55 -0500
Subject: [Archivesspace_Users_Group] "View Published" not resolving
 correct	web address
In-Reply-To: <SN2PR0801MB2287B2C665F8393AD7A77E71FE4D0@SN2PR0801MB2287.namprd08.prod.outlook.com>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0BEB@bmcmail2.PABMC.NET>
 <SN2PR0801MB2287B2C665F8393AD7A77E71FE4D0@SN2PR0801MB2287.namprd08.prod.outlook.com>
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0C0B@bmcmail2.PABMC.NET>

Mark,
Thanks much!  Works well now.

Jesse

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Cooper
Sent: Wednesday, February 01, 2017 10:30 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] "View Published" not resolving correct web address


Hi Jesse,



There are two settings in the config.rb file (in the config folder) that apply here:



AppConfig[:frontend_proxy_url]

For the url to your staff interface



AppConfig[:public_proxy_url]

For the url to your public interface



Update those and restart ArchivesSpace.



Best,

Mark


Mark Cooper
Technical Lead, Hosting and Support
LYRASIS
email: mark.cooper at lyrasis.org<mailto:mark.cooper at lyrasis.org>
skype: mark_c_cooper
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>>
Sent: Wednesday, February 1, 2017 7:07:52 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] "View Published" not resolving correct web address

After doing a test migration from ARCHON to AS (1.4.2), when I am logged into the staff interface, I can edit a RESOURCE.  I have the ability then to click on VIEW PUBLISHED to see what the record would look like on the public site.  But when I click on it, I get an error stating "This page cannot be opened."  I tried it with several different records with the same result.

Now, I can open the regular public interface separately and view the record, but to have that logged-in feature not working is concerning.

It appears that it is not resolving the correct web address. When I look in the address bar when I click on View Published, it is using localhost:8081 instead of my test site, bmc-asmigrate:8081. I don't know if this is a support or a setup issue. Has this been fixed in later release (remember, this is version 1.4.2) or if it is a setup issue?


[cid:image001.jpg at 01D27C77.AAD11FB0]



Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/d6be76f4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 31990 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/d6be76f4/attachment.jpg>

From jennyjing at brandeis.edu  Wed Feb  1 10:46:49 2017
From: jennyjing at brandeis.edu (Hong Jing)
Date: Wed, 1 Feb 2017 10:46:49 -0500
Subject: [Archivesspace_Users_Group] Job Posting: Sr. Systems Librarian @
	Brandeis University
Message-ID: <CAMFN=HYMPnHnkBAUZ8k+1BELZ5PVLAt6VmVkK+eSR30dCH+wHg@mail.gmail.com>

*Please excuse for cross-posting*

*Sr. Systems Librarian** (Job ID: 525826)*

Brandeis University seeks to hire a Senior Systems Librarian to be
responsible for administration and configuration of librarysystems, web
sites and applications.

*Key Responsibilities:*

?     Responsible for implementation, support and maintenance of
campus-wide library systems and applications, including but not limited to
Alma, Primo, ILLiad, Library Web Sites, Dspace and other systems as
implemented.

?     Responsible for providing leadership in partnership with the Manager
of Library Systems in planning new initiatives, and for facilitating
communication between the LTS technical staff and non-technical staff.

?     Responsible for enhancing library systems and applications, and
implementing and facilitating integration of library systems and
interoperability between library systems, other campus systems, and cloud
services.

?     Responsible for execution of all phases of projects to implement,
administer, configure, support and document the library systems; assist the
Manager of Library Systems in planning and coordinating such projects;
working with NetSys group to maintain and support the library servers;
providing back-up support to the Manager of Library Systems.

?     Responsible for operational activities including configuring,
troubleshooting and upgrading library systems, software and peripherals;
installing modules and software related to the library systems including,
but not limited to, Exlibris software systems, digital asset management
software.

?     Responsible for providing technical leadership, planning,
architecture, design and methodology for librarysystems initiatives and
implementations; in partnership with NetSys defining library systems
specifications,
planning and implementing data and digital asset preservation; analyzing
workflow and recommending process changes ; creating internal system and
training staff on library application and processes; keeping current with
technology developments and applications.

?     Develops and documents software programs to facilitate
interoperability between systems; works within established LTS software
development framework to develop software programs using standards and best
practices; automates data loads and feeds to and from the library systems;
other scripting as needed.

?     Analyzes users' data, application and reporting needs to design
processes and best practices; assists users with ad hoc report creation;
scripting for data transformation and reporting. Responsible for developing
and enhancing interfaces for user-facing services.

?     Responsible for supporting and maintaining all library systems and
services as backup for the Manager of Library Systems and the Systems
Librarian for E-Resources; Back-up core function of systems in the library and
be available for on-call

?     Responsible for working with LTS staff and university community on
planning for, implementing and administering systems for the public
discovery, storage and preservation of digital materials.

*Qualifications:*

*Required:*

   - MLS or MSI degree from an ALA-accredited institution of higher
   education
   - 5-7 years experience with library digital repositories; experience
   developing and managing library systems (Alma, Primo)
   - Proficiency with Perl (or PHP), SQL, HTML, XML required; May train
   others in functional area and interact with others across University and/or
   externally
   - Familiarity with metadata standards such as EAD, MARC, Dublic Core
   - Strong organizational, communication, customer service and
   interpersonal skills
   - Ability to work well with faculty, staff, and students. May make
   presentations to stakeholders
   - Strong analytical skills for complex software issues. Recommend and
   support the Manager of library system to make decision on process and
   workflow changes
   - Experience with open source software, applications, web tools and new
   technology
   - Ability to work with various constituencies and facilitate
   collaboration between them

*Preferred:*

   - Strong knowledge of Linux and Windows operating systems
   - Experience supporting campus-wide enterprise systems including
   integrated library systems, link resolvers, proxy servers, federated
   searching, digital asset management tools, electronic resource management
   systems
   - Strong technical and troubleshooting skills for complex applications.
   - Proficiency with relational databases, database back-ended applications
   - Experience with scripting languages and using APIs; experience with
   CSS, XML, XSL, XSLT and harvesting standards
   - Experience in a research library or academic library
   - Experience with some UX/usability testing methods
   - Experience in teaching library staff using new software/tools



*How to Apply:*

Submit cover letter and resume as a single document at
http://www.brandeis.edu/humanresources/jobs/external.html.  Elect option
for "External Applicant".   Sort the job listing by clicking the *Job
ID* column
heading.  Locate the desired job listing by Job ID.  Click the job title
and then Apply Now.



*Closing Statement:*

Brandeis University is an affirmative action/equal opportunity employer and
encourages minorities, women, disabled individuals, and eligible veterans
to apply. It is the policy of the University not to discriminate against
any applicant or employee on the basis of race, ancestry, color, religion,
sex, sexual orientation, age, genetic information, national origin,
disability, veteran status, or on the basis of any other legally protected
category.





Jenny Jing



Manager, Library Systems

Brandeis University Library



781-736-4698 <(781)%20736-4698>

JennyJing at brandeis.edu



-- 
Jenny Jing

Manager, Library Systems
Library & Technology Services,
Brandeis University Library

781-736-4698
JennyJing at brandeis.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/f0ca28e7/attachment.html>

From k-miller3 at northwestern.edu  Wed Feb  1 11:18:53 2017
From: k-miller3 at northwestern.edu (Karen Miller)
Date: Wed, 1 Feb 2017 16:18:53 +0000
Subject: [Archivesspace_Users_Group] Ingesting lcnaf
In-Reply-To: <SN1PR08MB1406F34C541AC5FA72CE5BCCF1740@SN1PR08MB1406.namprd08.prod.outlook.com>
References: <BN1PR07MB3277D1615ED12E4DB86D98C80740@BN1PR07MB327.namprd07.prod.outlook.com>
 <SN1PR08MB1406F34C541AC5FA72CE5BCCF1740@SN1PR08MB1406.namprd08.prod.outlook.com>
Message-ID: <03442c95c21e4568bb4bcaf59e63f3ea@evcspmbx05.ads.northwestern.edu>

Hello, Kate.

We are just starting to use the LCNAF plugin at Northwestern University. I can send you some of our documentation off list. We've described our best practices and the operations of the plugin in a bit more detail.

One thing I can say without including a lot of documentation is that we will not be using the plugin to import Subject records, only Agents. That's because when a Subject is imported using this plugin, individual Subject records are created for the preferred term (the MARC 150 field in the authority record) as well as for each of the non-preferred terms (the MARC 450 fields in the authority record). For example, an LSCH record with 4 non-preferred terms will be imported as 5 Subject records, one for the preferred term and one for each of the non-preferred terms, with no indication in the records for the non-preferred terms that they are references and should not be assigned, as well as no indication of the preferred term with which they are associated.

I have written some documentation with a lot of screenshots, which might be useful for you. I'll send it to you off list.

Best,
Karen


Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu
k-miller3 at northwestern.edu
874.467.3462

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Wednesday, January 25, 2017 12:46 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Ingesting lcnaf

Dear Kate,

This is a plugin but comes with a standard ArchivesSpace installation and is described in the user manual at https://docs.archivesspace.org/Default.htm#AgentsImportLCNAF.htm<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.archivesspace.org_Default.htm-23AgentsImportLCNAF.htm&d=CwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=NxowvYcR6MzGrS-X6DhbOLz5AcaT0wcYtLjA7pgcTRw&s=Yi5wychsv7BovafcVe0ZsPCCX7LIA2NYdPNTAH1Z_1U&e=>. It is also described and demonstrated in the Authorities overview video at http://docs.archivesspace.org/screencasts/KLNwebinars/17-AuthoritiesOverview.mp4<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.archivesspace.org_screencasts_KLNwebinars_17-2DAuthoritiesOverview.mp4&d=CwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=NxowvYcR6MzGrS-X6DhbOLz5AcaT0wcYtLjA7pgcTRw&s=OnpUy2MCPR_Jt1SuXcSX0pUivoWoUZRCFCVBuuxPkfo&e=> (it's discussed at about the 10:45 mark in the video). The ability to import subject headings from LCSH has been added since the instructions were last revised.

A few caveats: even though it's distributed with a standard ArchivesSpace, your system administrator has to have enabled use of this plugin for it to be available to you. Also, you have to have advanced data entry privileges or above to access it from the gear menu. You can try it out in the sandbox (http://sandbox.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__sandbox.archivesspace.org&d=CwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=NxowvYcR6MzGrS-X6DhbOLz5AcaT0wcYtLjA7pgcTRw&s=9PvY2vEX-w0zEuVWvw3gSyXPHeSYViscrJrHrnEGLAU&e=> - use the username admin and the password admin) if you don't have access locally and want to try it out.

This plugin is partially proof of concept - a demonstration of what could be done rather than a fully realized mechanism for importing all kinds of authorities. There are many other external databases that could interact with ArchivesSpace this way, and many ways this plugin itself could be improved, and I'd be very interested to hear if others have expanded on this plugin in their local installations.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)




From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A.
Sent: Wednesday, January 25, 2017 11:35 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Ingesting lcnaf

Searching list archives and google, I understand someone has written a plugin that ingests LCNAF.

Can anyone point me to documentation of what this plugin is meant to do?

If you use it, I'd appreciate any documentation you have written or reviews of your experiences with it?  Screenshots of agent records post-ingest would be extremely helpful.

Thanks!

Kate Bowers
Collections Services Archivist for Metadata, Systems, and Standards
Harvard University Archives
kate_bowers at harvard.edu<mailto:megan_sniffin-marinoff at harvard.edu>
voice: (617) 998-5238
fax: (617) 495-8011
web: http://nrs.harvard.edu/urn-3:hul.eresource:archives<https://urldefense.proofpoint.com/v2/url?u=http-3A__nrs.harvard.edu_urn-2D3-3Ahul.eresource-3Aarchives&d=CwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=NxowvYcR6MzGrS-X6DhbOLz5AcaT0wcYtLjA7pgcTRw&s=seIN0MaQ_42GwZ0DPppZll-oDaTFr287ONb5N50kr5U&e=>
Twitter: @k8_bowers




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/34aad3d2/attachment.html>

From christine.dibella at lyrasis.org  Wed Feb  1 12:12:11 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 1 Feb 2017 17:12:11 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate
	available - v1.5.3-RC1
Message-ID: <SN1PR08MB1406392897A5A57BF0AB5E87F14D0@SN1PR08MB1406.namprd08.prod.outlook.com>

Dear ArchivesSpace members,

We are pleased to announce that a release candidate - v1.5.3-RC1 (https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3-RC1) - is now available for download and testing purposes. This minor release has some bug fixes, including a fix for the issue with components being exported in EAD in a different order from how they appear in the staff interface (https://archivesspace.atlassian.net/browse/AR-1620), as well as improvements to overall performance. It features work from our development partner, Hudson Molonglo (HM), as well as contributions from community members and release management from our new Tech Lead, Laney McGlohon.

Please try out this release candidate as you are able over the next few days and let us know if you experience any problems. If you don't wish to download anything at this time, you can still test drive the release candidate on our test site, http://test.archivesspace.org, using the standard administrative login.

There are two ways to let us know the results of your testing:


*         If you have a JIRA account, put a comment on the relevant JIRA issue for the bug fix or feature. (If you don't already have a JIRA account, you can sign up directly from http://development.archivesspace.org<http://development.archivesspace.org/> by choosing the Create an account option on the login page.)

*         If you have feedback that spans issues, or if you'd prefer not to work in JIRA, email it directly to me.

If at all possible, please submit your feedback no later than Monday, February 6.

It's probably obvious, but what we can address right now is limited to making sure the bug fixes and additional features in this release are working as they should and not impacting other functions unintentionally. You may send us comments and ideas on anything at any time, of course, but, as you would expect, we won't be able to undertake work outside these areas in the narrow window before this release is out the door, so to speak.

Barring unforeseen issues, we expect the production release of 1.5.3 to come out by February 10. We expect the next major release of ArchivesSpace, 1.6.0, to come out in March.

Thanks to HM for all their work on this release candidate, to our community members that contributed code, and to those on the Prioritization and Testing sub-teams who identified and tested the needed bug fixes. If you have any questions, or if you notice any issues while testing, please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHome]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/13b610eb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/13b610eb/attachment.jpg>

From adrien_hilton at harvard.edu  Wed Feb  1 13:15:18 2017
From: adrien_hilton at harvard.edu (Hilton, Adrien)
Date: Wed, 1 Feb 2017 18:15:18 +0000
Subject: [Archivesspace_Users_Group] Changing top containers for archival
	objects in bulk
Message-ID: <CY1PR07MB23307789E415B556F09FDE9B884D0@CY1PR07MB2330.namprd07.prod.outlook.com>

Hello ASpace community,

We recently started using AS for our archival description. Previous practice involved hand-encoding EAD in oXygen. We did not use containers but rather consecutive <unitid>s that were machine generated at the end of description. Processing involved (and continues to involve) a lot of both physical and intellectual arranging and rearranging right up until those <unitid>s were created.

We're having a difficult time with data entry in AS. For example, a bunch of archival objects are created and assigned to Top Container 1. But then we find some more (physical) material that needs to go in Box 1. We shift folders (physically) from Box  1 to Box 2. Do we have to open each archival object that we want moved and assign it to Top Container 2?

I know we could physically leave said folders at the end, etc. But first I just want to know if AS allows for bulk editing of archival objects that are already assigned a Top Container to a different Top Container. Am I missing something? Could I use the API for this?

For practice sake, what are others doing in this case? Are you ensuring physical order is established before data entry?

Many thanks in advance,
Adrien


Adrien Hilton
Head of the Manuscript Section
Houghton Library
Harvard University
Cambridge, MA 02138
adrien_hilton at harvard.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/82af5cf6/attachment.html>

From mbliese at lutheranhistory.org  Wed Feb  1 15:06:05 2017
From: mbliese at lutheranhistory.org (Mark Bliese)
Date: Wed, 1 Feb 2017 20:06:05 +0000
Subject: [Archivesspace_Users_Group] Problems with service starting
Message-ID: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD310@Wyneken.chinet.local>

Our organization is installing ASpace. I have followed the directions for install, running ASpace against MYSQL, and installing ASpace as a Windows Service.

Database has been created, ArchivesSpaceService and ArchivesSpaceServicew have been created, with one hitch.

When service.bat is run, it creates the two files but includes the line, "There was a problem installing the service...please check the settings."
If I run ArchivesSpaceServicew the service is stopped, attempting to launch it does not work and the log file contains the lines:
[2017-02-01 13:53:27] [error] [ 4184] Failed to execute process
[2017-02-01 13:53:27] [error] [ 4184] The directory name is invalid.
[2017-02-01 13:53:27] [error] [ 4184] ServiceStart returned 5
[2017-02-01 13:53:27] [error] [ 4184] The directory name is invalid.
[2017-02-01 13:53:27] [info]  [ 5180] Run service finished.
[2017-02-01 13:53:27] [info]  [ 5180] Commons Daemon procrun finished

I am not sure what directory it is looking for, and the only thing that I had different than the instructions is where Java resides (I have another application that uses Java and MySQL where Java is installed as Oracle\Java\Javapath).

Any assistance here?

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image003.png at 01D27C94.54062AA0]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/42284c2e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 36655 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/42284c2e/attachment.png>

From library at princeofpeaceabbey.org  Wed Feb  1 15:47:47 2017
From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org)
Date: Wed, 01 Feb 2017 14:47:47 -0600
Subject: [Archivesspace_Users_Group] Problems with service starting
In-Reply-To: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD310@Wyneken.chinet.local>
Message-ID: <20170201144747.Horde.z-JEgAEhMDzNa8IEhwAyd21@gator3088.hostgator.com>

Mark

if it the that happened to me. You will need to go to System32 and  
right click on the AS service and there you can choose a different  
java I had a choice of three so took the middle one and it worked.

Br Raphael
Quoting Mark Bliese <mbliese at lutheranhistory.org>:

> Our organization is installing ASpace. I have followed the  
> directions for install, running ASpace against MYSQL, and installing  
> ASpace as a Windows Service.
>
> Database has been created, ArchivesSpaceService and  
> ArchivesSpaceServicew have been created, with one hitch.
>
> When service.bat is run, it creates the two files but includes the  
> line, "There was a problem installing the service...please check the  
> settings."
> If I run ArchivesSpaceServicew the service is stopped, attempting to  
> launch it does not work and the log file contains the lines:
> [2017-02-01 13:53:27] [error] [ 4184] Failed to execute process
> [2017-02-01 13:53:27] [error] [ 4184] The directory name is invalid.
> [2017-02-01 13:53:27] [error] [ 4184] ServiceStart returned 5
> [2017-02-01 13:53:27] [error] [ 4184] The directory name is invalid.
> [2017-02-01 13:53:27] [info]  [ 5180] Run service finished.
> [2017-02-01 13:53:27] [info]  [ 5180] Commons Daemon procrun finished
>
> I am not sure what directory it is looking for, and the only thing  
> that I had different than the instructions is where Java resides (I  
> have another application that uses Java and MySQL where Java is  
> installed as Oracle\Java\Javapath).
>
> Any assistance here?
>
> Mark J. Bliese
> IT & Research
> Concordia Historical Institute
> 804 Seminary Place
> Saint Louis, MO 63105
> Ph: 314-505-7907
> Fax: 314-505-7901
> mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
> http://concordiahistoricalinstitute.org
>
> [cid:image003.png at 01D27C94.54062AA0]
>
> Confidentiality Notice: This e-mail message, including any  
> attachments, originates from Concordia Historical Institute of The  
> Lutheran Church-Missouri Synod. It contains information which may be  
> confidential or privileged, and is therefore restricted to and for  
> the sole use of the intended recipient(s). If you are not the  
> intended recipient or the person responsible for delivering the  
> e-mail to the intended recipient, be advised that you have received  
> this e-mail in error and that any use, dissemination, forwarding,  
> copying or printing of this e-mail is strictly prohibited. This  
> e-mail is the sole property of Concordia Historical Institute and  
> may not be distributed by any means without this disclaimer. If you  
> are not the intended recipient, please contact the sender by reply  
> e-mail and destroy all copies of the original message and delete the  
> message from your computer and network systems. Please accept our  
> thanks, in advance.




From christine.dibella at lyrasis.org  Wed Feb  1 16:34:55 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 1 Feb 2017 21:34:55 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - February 2017
Message-ID: <SN1PR08MB14067F929C6B0C5C9BBE88A1F14D0@SN1PR08MB1406.namprd08.prod.outlook.com>

[ASpaceOrgHome.jpg]

February 2017 Update


Development

We are pleased to announce that a release candidate - v1.5.3-RC1 (https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3-RC1) - is now available for download and testing purposes. This minor release has some bug fixes, including a fix for the issue with components being exported in EAD in a different order from how they appear in the staff interface (https://archivesspace.atlassian.net/browse/AR-1620), as well as improvements to overall performance. It features work from our development partner, Hudson Molonglo (HM), as well as contributions from community members and release management from our new Tech Lead, Laney McGlohon.

Please try out this release candidate as you are able over the next few days and let us know if you experience any problems. If you don't wish to download anything at this time, you can still test drive the release candidate on our test site, http://test.archivesspace.org, using the standard administrative login.

There are two ways to let us know the results of your testing:

*         If you have a JIRA account, put a comment on the relevant JIRA issue for the bug fix or feature. (If you don't already have a JIRA account, you can sign up directly from http://development.archivesspace.org<http://development.archivesspace.org/> by choosing the Create an account option on the login page.)

*         If you have feedback that spans issues, or if you'd prefer not to work in JIRA, email it directly to Christine (christine.dibella at lyrasis.org).

If at all possible, please submit your feedback no later than Monday, February 6. Barring unforeseen issues, we expect the production release of 1.5.3 to come out by February 10. We expect the next major release of ArchivesSpace, 1.6.0, to come out in March.

Thanks to HM for all their work on this release candidate, to our community members that contributed code, and to those on the Prioritization and Testing sub-teams who identified and tested the needed bug fixes.



Technology and Development Roadmap

The ArchivesSpace team has shared a draft Technology and Development Roadmap with the Community at https://archivesspace.atlassian.net/wiki/display/ADC/Road+Map. This roadmap is a planning and communication tool to help the community know what to expect in terms of future development work and aid in planning for upcoming releases and application upgrades. The roadmap is a living document that will continue to be updated regularly. By its nature, the roadmap has more detail in the near term but more tentative information about improvements planned farther out. Details about each release will be clearer closer to each release date. The roadmap will be available on the ArchivesSpace wiki at and updated there as plans coalesce and progress is made. Feel free to send us feedback at ArchivesSpaceHome at lyrasis.org.


Staffing News

New Program Manager

LYRASIS, the organizational home for ArchivesSpace, is delighted to announce that Christine Di Bella is the new ArchivesSpace Program Manager.

Christine's extensive knowledge of ArchivesSpace, her close connection to its community, and her deep and varied experience in the archival profession all make her uniquely well-qualified for this position.  As Program Manager, Christine will play a key role working with the community to set the strategy and goals for ArchivesSpace.  The Program Manager is central to the success of the program, and works closely and collaboratively with the ArchivesSpace community, advisory groups and Board to ensure success. Christine will be involved in all aspects of the program, and serve as a key spokesperson and advocate for the program.

Christine has been with LYRASIS's ArchivesSpace team since 2014. In her most recent role as Community Outreach Manager she participated in a number of activities to strengthen the program and engage our community in its future in part by improving both the quality and timeliness of our communication to members and non-members. She managed the ArchivesSpace training program and led the planning efforts for the 2015 and 2016 Member Forums.

While at LYRASIS, Christine been a critical contributor to both ArchivesSpace and LYRASIS programs and services. This important relationship between ArchivesSpace and LYRASIS will be served by having such a dedicated member of both teams in this position.

Before joining the ArchivesSpace team, Christine managed the archives at the Institute for Advanced Study, led a consortial survey project for the Philadelphia Area Consortium of Special Collections Libraries (PACSCL), and worked on large processing projects at institutions including the 92nd Street Y and the University of Michigan.   Christine earned her Bachelor's degree in English from Wesleyan University and her Masters of Science in Information from the School of Information at the University of Michigan. She also holds a Digital Archives Specialist (DAS) certificate from the Society of American Archivists.

Christine and Laney McGlohon, the ArchivesSpace Tech Lead, report to Laurie Arp, LYRASIS's Director of Collections Services & Community Supported Software.  They will work together to support the ArchivesSpace community and improve the ArchivesSpace application.

Christine's new role is effective immediately. Feel free to get in touch with questions or suggestions at christine.dibella at lyrasis.org.



An Introduction from Our New Tech Lead, Laney McGlohon

"I would like to introduce myself to the ArchivesSpace community. I'm Laney McGlohon, the ArchivesSpace Technical Lead.  I started on Monday, January 23, 2017, and will be based in Atlanta, Georgia. I'm an information scientist, software developer, librarian, and data wrangler. I have been writing software for over 30 years and have worked in many different kinds of libraries - public, newspaper, academic, and cultural heritage institutions. My experience with special collections and archives spans more than seven years during which time I worked full-time at the Getty Research Institute (GRI) in Los Angeles and as a consultant and volunteer at the Museum of Ventura County California. I was responsible for managing the Archivists' Toolkit (AT) installations and the import of finding aids in many different digital formats and the export of EADs into the institutional discovery systems and the Online Archive of California. Before I left the GRI in 2014, I had several opportunities to work with the early migration tool from AT to ArchivesSpace and, upon my arrival at Stanford University Libraries, I assisted the University Archivist in the AT migration to the local ArchivesSpace installation.

I'm very excited to have this opportunity to work with archivists and other special collections-oriented colleagues again.  I look forward to working with all of you on improving the ArchivesSpace application and enhancing the deployment and usability of the software. Expect to hear more about the engagement of a broader set of developers in future development of the application. I will be attending Code4Lib 2017 anticipating opportunities to connect with like-minded people there.

You'll be hearing more from Christine and me in the weeks to come about future plans, but in the meantime, feel free to get in touch at any point. I can be reached at laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>."



Membership Update

Our new members since January 6 include:

*         Artspace San Antonio

*         Concordia Historical Institute (St. Louis, Missouri)

*         Cornell University

*         North Carolina State University

As of February 1, we have 317 General members, 11 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> for more information.


ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/54b5fd42/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 9827 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170201/54b5fd42/attachment.jpg>

From jteitelbaum at pabmc.net  Thu Feb  2 10:04:50 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Thu, 2 Feb 2017 10:04:50 -0500
Subject: [Archivesspace_Users_Group] ARCHON sort titles not migrating
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D2A085D@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D1E690D@bmcmail2.PABMC.NET>
 <551D255B-C5A2-40ED-9428-9713442445F6@illinois.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D2A07C3@bmcmail2.PABMC.NET>
 <SN1PR08MB140682296700D9E4E43FB1EDF14B0@SN1PR08MB1406.namprd08.prod.outlook.com>
 <C6AAE365E91EEC43876ABA64C804C6E4213D2A085D@bmcmail2.PABMC.NET>
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D2A0DC3@bmcmail2.PABMC.NET>

Hello,
A similar thing happens in the FINDING AID DATA fields when Archon records migrated over.  Notice the titles read ?Archon Finding Aid Title.?  So when I try to Print a PDF of the finding aid, the title of the collection is ?Archon Finding Aid Title, ID #08##z2j.?

Is there a simple migration solution that I am missing, or will I need to edit each field afterwards?  Thanks.

Jesse

[cid:image001.jpg at 01D27D3B.CAB15F10]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse
Sent: Monday, January 30, 2017 11:18 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ARCHON sort titles not migrating


This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

Thanks Christine.  I did find the fields you mentioned and I was able to manually edit them.

Jesse

Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>




From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Monday, January 30, 2017 10:26 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ARCHON sort titles not migrating

Dear Jesse,

The Archon migration tool was refactored in November 2015. Aside from a small change made in September 2016 to fix a bug with parsing certain kinds of digital objects, further changes have not been made since then.

There is a field called ?Finding Aid Filing Title?  in ArchivesSpace which provides the capability of differentiating between how the resource is represented in its title field and formal finding aid title field and how it appears in browse and search lists. If there?s a value in Finding Aid Filing Title, this is what appears in browse and search lists in the staff interface. From a functional standpoint, that would be the place to enter your Sort Titles from Archon.

Have others migrating from Archon had the same experience? How have you addressed it with your migrated data?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse
Sent: Monday, January 30, 2017 9:45 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ARCHON sort titles not migrating

Chris,
Before I try to find a plug-in for this, do you know if this would have been addressed in the 1.5.2?

Jesse

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Prom, Christopher John
Sent: Tuesday, January 24, 2017 4:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ARCHON sort titles not migrating

Hi,

According the the specs, this should be migrating into a user defined field with value "Sort Title"?can you check to see if it ended up there, Jesse?  I don't think, however, that ASpace would sort on that field w/out a plugin.

Thanks,

Chris Prom
Univeristy of Illinois

On Jan 24, 2017, at 2:48 PM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We are migrating ARCHON records to  AS 1.4.2 and the collection titles are coming over alphabetically by title and not the ?sort title.?  For example, in ARCHON, the ?Papers of John Doe? are listed under D for DOE, but when brought over to AS, all the collections beginning with ?Papers of?? are listed under ?P.?

Does 1.5.2 fix this?  Or is a plug-in required?  Thanks.

Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.house.state.pa.us_BMC_archives&d=DwMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=jGJMaTc-8I-z6_tkoj_Qyi4UF1KtYBfcz4s2Ly33jmw&m=Fsumxsjg4nAyrgdkZVr02h3hJL27I73OFfF1qB3SUM8&s=MYH4dBFjveOjKgrqODI0pQuJgInPsGw4THXuqXGJHHs&e=>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/9b31b3ae/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 27449 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/9b31b3ae/attachment.jpg>

From mbliese at lutheranhistory.org  Thu Feb  2 10:45:52 2017
From: mbliese at lutheranhistory.org (Mark Bliese)
Date: Thu, 2 Feb 2017 15:45:52 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
Message-ID: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D39.245788D0]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/dc529a35/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/dc529a35/attachment.png>

From bfinberg at okeeffemuseum.org  Thu Feb  2 11:36:17 2017
From: bfinberg at okeeffemuseum.org (Ben Finberg)
Date: Thu, 2 Feb 2017 16:36:17 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
Message-ID: <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D37.CBA72D90]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/bcfdaad0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/bcfdaad0/attachment-0001.png>

From mbliese at lutheranhistory.org  Thu Feb  2 12:00:15 2017
From: mbliese at lutheranhistory.org (Mark Bliese)
Date: Thu, 2 Feb 2017 17:00:15 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
 <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
Message-ID: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>

Yes, I am running Windows.

I stopped the Windows Service, then launched the ArchivesSpace.bat file
I then tried to access the app in the browser. Still no go.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D43.88B379B0]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/3a9a45ee/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/3a9a45ee/attachment.png>

From bfinberg at okeeffemuseum.org  Thu Feb  2 12:15:49 2017
From: bfinberg at okeeffemuseum.org (Ben Finberg)
Date: Thu, 2 Feb 2017 17:15:49 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
 <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>
Message-ID: <MWHPR11MB2046F9F441196203EC836BBFC84C0@MWHPR11MB2046.namprd11.prod.outlook.com>

So although I'm not an ArchivesSpace expert (like, at ALL), I'm pretty decent at general computer troubleshooting. The fact that you couldn't run ArchivesSpace using the foreground batch file eliminates the Windows service as the culprit, so we're at least making a little progress.

A few initial thoughts/questions I have at this point:


*         What version of Windows are you running? Is it a dedicated PC for ArchivesSpace or is it running other services too? Is it a new Windows install or has it been around for a while?

*         As an experiment, have you tried totally disabling your Windows firewall(s), for all networks? Do you have 3rd party antivirus protection that might have a built-in firewall that's blocking the ArchivesSpace ports? Have you tried browsing both from a browser on the ArchivesSpace PC (to http://localhost:8081) and from another computer (to http://aspacePCname:8081)?

*         There was a thread on this newsgroup yesterday that mentioned an issue with multiple versions of Java causing a conflict. Take a peek in C:\Program Files (x86)\Java...do you see multiple jrexxx folders in there?


Benjamin Finberg, Director of IT and Operations
The Georgia O'Keeffe Museum
505.946.1057
217 Johnson St., Santa Fe, NM  87501
www.okeeffemuseum.org<http://www.okeeffemuseum.org/>

A Great American Artist, a Great American Story. Explore the remarkable career of Georgia O'Keeffe through her artwork, the objects and places that were meaningful to her, and the experiences that defined her life.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 10:00 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Yes, I am running Windows.

I stopped the Windows Service, then launched the ArchivesSpace.bat file
I then tried to access the app in the browser. Still no go.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D3C.617B8380]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/a16523d8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/a16523d8/attachment.png>

From mbliese at lutheranhistory.org  Thu Feb  2 13:02:16 2017
From: mbliese at lutheranhistory.org (Mark Bliese)
Date: Thu, 2 Feb 2017 18:02:16 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <MWHPR11MB2046F9F441196203EC836BBFC84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
 <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>
 <MWHPR11MB2046F9F441196203EC836BBFC84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
Message-ID: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD5FF@Wyneken.chinet.local>

Dear Ben,

Thank you for taking the time do discuss this. I have ASpace loaded on a Windows Server 2008 R2. This has been in place for a number of years.
Before I installed the Windows service and the changes necessary to run against MySQL, I ran it against the demo database. No problems accessing that.

I am checking with another vendor of ours where their app uses MySQL and Java to make sure that any changes I make don't cripple their app.
There is only one system variable that I left alone because of that. Once I hear back from them, I can make a change and see if that allows me access.

To answer your question about the firewall, I have checked that and it is ok. I have tried a browser both on the server and on a client to see if I can access the database.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 11:16 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

So although I'm not an ArchivesSpace expert (like, at ALL), I'm pretty decent at general computer troubleshooting. The fact that you couldn't run ArchivesSpace using the foreground batch file eliminates the Windows service as the culprit, so we're at least making a little progress.

A few initial thoughts/questions I have at this point:


*         What version of Windows are you running? Is it a dedicated PC for ArchivesSpace or is it running other services too? Is it a new Windows install or has it been around for a while?

*         As an experiment, have you tried totally disabling your Windows firewall(s), for all networks? Do you have 3rd party antivirus protection that might have a built-in firewall that's blocking the ArchivesSpace ports? Have you tried browsing both from a browser on the ArchivesSpace PC (to http://localhost:8081) and from another computer (to http://aspacePCname:8081)?

*         There was a thread on this newsgroup yesterday that mentioned an issue with multiple versions of Java causing a conflict. Take a peek in C:\Program Files (x86)\Java...do you see multiple jrexxx folders in there?


Benjamin Finberg, Director of IT and Operations
The Georgia O'Keeffe Museum
505.946.1057
217 Johnson St., Santa Fe, NM  87501
www.okeeffemuseum.org<http://www.okeeffemuseum.org/>

A Great American Artist, a Great American Story. Explore the remarkable career of Georgia O'Keeffe through her artwork, the objects and places that were meaningful to her, and the experiences that defined her life.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 10:00 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Yes, I am running Windows.

I stopped the Windows Service, then launched the ArchivesSpace.bat file
I then tried to access the app in the browser. Still no go.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D4B.7B844190]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/b07d4d07/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/b07d4d07/attachment.png>

From PGalligan at rockarch.org  Thu Feb  2 15:13:06 2017
From: PGalligan at rockarch.org (Galligan, Patrick)
Date: Thu, 2 Feb 2017 20:13:06 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD5FF@Wyneken.chinet.local>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
 <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>
 <MWHPR11MB2046F9F441196203EC836BBFC84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD5FF@Wyneken.chinet.local>
Message-ID: <1a3a378bb15e4f5d9cc8d42349e6f3f4@RACEX13.ad.rockarchive.org>

Mark,

Can you check what the Archivesspace.out log is saying when you run the service?

Even if it never starts up ArchivesSpace, it should give you an error message saying what's going on.

-Patrick Galligan

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 02, 2017 1:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Dear Ben,

Thank you for taking the time do discuss this. I have ASpace loaded on a Windows Server 2008 R2. This has been in place for a number of years.
Before I installed the Windows service and the changes necessary to run against MySQL, I ran it against the demo database. No problems accessing that.

I am checking with another vendor of ours where their app uses MySQL and Java to make sure that any changes I make don't cripple their app.
There is only one system variable that I left alone because of that. Once I hear back from them, I can make a change and see if that allows me access.

To answer your question about the firewall, I have checked that and it is ok. I have tried a browser both on the server and on a client to see if I can access the database.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 11:16 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

So although I'm not an ArchivesSpace expert (like, at ALL), I'm pretty decent at general computer troubleshooting. The fact that you couldn't run ArchivesSpace using the foreground batch file eliminates the Windows service as the culprit, so we're at least making a little progress.

A few initial thoughts/questions I have at this point:


*         What version of Windows are you running? Is it a dedicated PC for ArchivesSpace or is it running other services too? Is it a new Windows install or has it been around for a while?

*         As an experiment, have you tried totally disabling your Windows firewall(s), for all networks? Do you have 3rd party antivirus protection that might have a built-in firewall that's blocking the ArchivesSpace ports? Have you tried browsing both from a browser on the ArchivesSpace PC (to http://localhost:8081) and from another computer (to http://aspacePCname:8081)?

*         There was a thread on this newsgroup yesterday that mentioned an issue with multiple versions of Java causing a conflict. Take a peek in C:\Program Files (x86)\Java...do you see multiple jrexxx folders in there?


Benjamin Finberg, Director of IT and Operations
The Georgia O'Keeffe Museum
505.946.1057
217 Johnson St., Santa Fe, NM  87501
www.okeeffemuseum.org<http://www.okeeffemuseum.org/>

A Great American Artist, a Great American Story. Explore the remarkable career of Georgia O'Keeffe through her artwork, the objects and places that were meaningful to her, and the experiences that defined her life.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 10:00 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Yes, I am running Windows.

I stopped the Windows Service, then launched the ArchivesSpace.bat file
I then tried to access the app in the browser. Still no go.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D66.DABAD820]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/bc2d5c13/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/bc2d5c13/attachment.png>

From mbliese at lutheranhistory.org  Thu Feb  2 15:27:37 2017
From: mbliese at lutheranhistory.org (Mark Bliese)
Date: Thu, 2 Feb 2017 20:27:37 +0000
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser
In-Reply-To: <1a3a378bb15e4f5d9cc8d42349e6f3f4@RACEX13.ad.rockarchive.org>
References: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD49C@Wyneken.chinet.local>
 <MWHPR11MB2046AB1ABAC6C62ACAB1D980C84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD594@Wyneken.chinet.local>
 <MWHPR11MB2046F9F441196203EC836BBFC84C0@MWHPR11MB2046.namprd11.prod.outlook.com>
 <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD5FF@Wyneken.chinet.local>
 <1a3a378bb15e4f5d9cc8d42349e6f3f4@RACEX13.ad.rockarchive.org>
Message-ID: <4FD06C925D5BFC4EBEDCF4EE5F94B7AF3A9DD690@Wyneken.chinet.local>

Patrick,

The service is running fine. No errors appear in the log.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick
Sent: Thursday, February 02, 2017 2:13 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Mark,

Can you check what the Archivesspace.out log is saying when you run the service?

Even if it never starts up ArchivesSpace, it should give you an error message saying what's going on.

-Patrick Galligan

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 02, 2017 1:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Dear Ben,

Thank you for taking the time do discuss this. I have ASpace loaded on a Windows Server 2008 R2. This has been in place for a number of years.
Before I installed the Windows service and the changes necessary to run against MySQL, I ran it against the demo database. No problems accessing that.

I am checking with another vendor of ours where their app uses MySQL and Java to make sure that any changes I make don't cripple their app.
There is only one system variable that I left alone because of that. Once I hear back from them, I can make a change and see if that allows me access.

To answer your question about the firewall, I have checked that and it is ok. I have tried a browser both on the server and on a client to see if I can access the database.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 11:16 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

So although I'm not an ArchivesSpace expert (like, at ALL), I'm pretty decent at general computer troubleshooting. The fact that you couldn't run ArchivesSpace using the foreground batch file eliminates the Windows service as the culprit, so we're at least making a little progress.

A few initial thoughts/questions I have at this point:


*         What version of Windows are you running? Is it a dedicated PC for ArchivesSpace or is it running other services too? Is it a new Windows install or has it been around for a while?

*         As an experiment, have you tried totally disabling your Windows firewall(s), for all networks? Do you have 3rd party antivirus protection that might have a built-in firewall that's blocking the ArchivesSpace ports? Have you tried browsing both from a browser on the ArchivesSpace PC (to http://localhost:8081) and from another computer (to http://aspacePCname:8081)?

*         There was a thread on this newsgroup yesterday that mentioned an issue with multiple versions of Java causing a conflict. Take a peek in C:\Program Files (x86)\Java...do you see multiple jrexxx folders in there?


Benjamin Finberg, Director of IT and Operations
The Georgia O'Keeffe Museum
505.946.1057
217 Johnson St., Santa Fe, NM  87501
www.okeeffemuseum.org<http://www.okeeffemuseum.org/>

A Great American Artist, a Great American Story. Explore the remarkable career of Georgia O'Keeffe through her artwork, the objects and places that were meaningful to her, and the experiences that defined her life.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 10:00 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Yes, I am running Windows.

I stopped the Windows Service, then launched the ArchivesSpace.bat file
I then tried to access the app in the browser. Still no go.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Finberg
Sent: Thursday, February 02, 2017 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser

Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Bliese
Sent: Thursday, February 2, 2017 8:46 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace not accessible using browser

I have installed ASpace, set up the service and database using the instructions.
Service is running, ports have been added to the firewall for inbound access.

I am not able to connect to ASpace from a client browser or from a browser on the server.

There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance.

Mark J. Bliese
IT & Research
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: 314-505-7907
Fax: 314-505-7901
mbliese at lutheranhistory.org<mailto:mbliese at lutheranhistory.org>
http://concordiahistoricalinstitute.org

[cid:image001.png at 01D27D60.806FF900]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/2a234347/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36663 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/2a234347/attachment.png>

From robin_wendler at harvard.edu  Thu Feb  2 15:45:57 2017
From: robin_wendler at harvard.edu (Wendler, Robin King)
Date: Thu, 2 Feb 2017 20:45:57 +0000
Subject: [Archivesspace_Users_Group] error saving an Archival Object
Message-ID: <DM2PR07MB1563E888DE772B80D4C06D959E4C0@DM2PR07MB1563.namprd07.prod.outlook.com>

Hello, ASpacers,
         When saving the archival object below, changed only by adding a single space preceding "Tours" in the title, we get the following error message:

[cid:image001.png at 01D27D6A.07258330]

The same error usually occurs if we try to change other archival object records attached to this resource record, but not always. One I was able to change, but received the error when I tried to change it back. Another I could change and change back without encountering the error. The resource record itself can be changed.  Any ideas about why this is happening and what we can do to clear it up?

Thanks for your thoughts,
Robin

Robin Wendler
Library Technology Services
Harvard University
90 Mt. Auburn St.
Cambridge, MA 02138
617-495-3724
r_wendler at harvard.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/df0aba4b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 116837 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/df0aba4b/attachment.png>

From atummino at sunymaritime.edu  Thu Feb  2 16:07:41 2017
From: atummino at sunymaritime.edu (Tummino, Annie)
Date: Thu, 2 Feb 2017 21:07:41 +0000
Subject: [Archivesspace_Users_Group] Agent Records Associated with Archival
	Objects
Message-ID: <870431a184564f85b19614cb95e10cb3@EX02.sunymaritime.edu>

Hello,

Apologies if this has already been addressed.

I am working on a collection that gets heavy use by genealogists. I am weighing out including names within the archival description for files versus creating agent records and linking them to the files. However, in this test, I noticed that agents associated with archival objects are not linking back to the collection on the public interface:

http://sunymaritimearchives.libraryhost.com/agents/26?agent_type=agent_person

Under Related Collections it says No Records.

Based on perusing the new PUI test site, I *think* maybe this is something that is just not working now that will be fixed when it gets released? Could anyone confirm this?

I am in the midst of designing a project for students that is supposed to start in a week - I'd like to have them create agent records, but not if it won't display correctly?

Best,
Annie

--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>
718-409-7228


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/673f7519/attachment.html>

From noah.huffman at duke.edu  Thu Feb  2 16:37:34 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Thu, 2 Feb 2017 21:37:34 +0000
Subject: [Archivesspace_Users_Group] error saving an Archival Object
In-Reply-To: <DM2PR07MB1563E888DE772B80D4C06D959E4C0@DM2PR07MB1563.namprd07.prod.outlook.com>
References: <DM2PR07MB1563E888DE772B80D4C06D959E4C0@DM2PR07MB1563.namprd07.prod.outlook.com>
Message-ID: <CO1PR05MB3295F7D148E11A72C12BEBBE64C0@CO1PR05MB329.namprd05.prod.outlook.com>

Robin,

Here's an unresolved JIRA issue describing this problem: https://archivesspace.atlassian.net/browse/AR-1326

It tends to happen when you try to edit an archival object record that has been transferred from another resource record.

As far as I know, there are a couple of fixes for this:

1.       Resequence your entire ASpace database.  To do this, shut down ASpace, modify config.rb (#AppConfig[:resequence_on_startup] = True), and restart.  Beware that resequencing a large database will take a long time, but this should prevent the same error from occurring in other records.

2.       Install this plugin that allows you to resequence only the resource record where the error occurs: https://github.com/archivesspace/resync

-Noah

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Wendler, Robin King
Sent: Thursday, February 02, 2017 3:46 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] error saving an Archival Object

Hello, ASpacers,
         When saving the archival object below, changed only by adding a single space preceding "Tours" in the title, we get the following error message:

[cid:image001.png at 01D27D70.E6CB7BB0]

The same error usually occurs if we try to change other archival object records attached to this resource record, but not always. One I was able to change, but received the error when I tried to change it back. Another I could change and change back without encountering the error. The resource record itself can be changed.  Any ideas about why this is happening and what we can do to clear it up?

Thanks for your thoughts,
Robin

Robin Wendler
Library Technology Services
Harvard University
90 Mt. Auburn St.
Cambridge, MA 02138
617-495-3724
r_wendler at harvard.edu<mailto:r_wendler at harvard.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/f7275aac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 116837 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/f7275aac/attachment-0001.png>

From Gregory.Farr at AustenRiggs.net  Thu Feb  2 16:47:37 2017
From: Gregory.Farr at AustenRiggs.net (Gregory.Farr at AustenRiggs.net)
Date: Thu, 2 Feb 2017 16:47:37 -0500
Subject: [Archivesspace_Users_Group] Agent Records Associated with
	Archival	Objects
In-Reply-To: <870431a184564f85b19614cb95e10cb3@EX02.sunymaritime.edu>
References: <870431a184564f85b19614cb95e10cb3@EX02.sunymaritime.edu>
Message-ID: <OFD546FE1D.8C9096EE-ON852580BB.0076887A-852580BB.0077B732@AUSTENRIGGS.NET>

Hello,

>From what I understand working with AS, agent records only link back to 
'collections' if the agents name is included in the top record of the 
collection that denotes all the finding aid data, etc.. If this is in fact 
true, it seems like a shortcoming, since it would be ideal to see all the 
records created by or associated with the agent when one enters an agent 
record based on the agent being linked to such records. I have agents 
linked with most of the archival and digital object records I have 
created, and none of this information shows up on the PUI ... only the 
collection the agent is related to when the agent, again, is additionally 
linked to the top collection record. 

I am responding because I would like to see it otherwise if possible. 

Best regards,
Greg


Gregory D. Farr, MLIS, CA
Librarian/Archivist
Erikson Institute for Education and Research
The Austen Riggs Center
25 Main Street
Stockbridge, MA  01262
Phone: (413) 931-5259  FAX (413) 298-4020
gregory.farr at austenriggs.net



From:   "Tummino, Annie" <atummino at sunymaritime.edu>
To:     Archivesspace Users Group 
<archivesspace_users_group at lyralists.lyrasis.org>, 
Date:   02/02/2017 04:07 PM
Subject:        [Archivesspace_Users_Group] Agent Records Associated with 
Archival        Objects
Sent by:        archivesspace_users_group-bounces at lyralists.lyrasis.org



Hello,
 
Apologies if this has already been addressed. 
 
I am working on a collection that gets heavy use by genealogists. I am 
weighing out including names within the archival description for files 
versus creating agent records and linking them to the files. However, in 
this test, I noticed that agents associated with archival objects are not 
linking back to the collection on the public interface:
 
http://sunymaritimearchives.libraryhost.com/agents/26?agent_type=agent_person
 
Under Related Collections it says No Records. 
 
Based on perusing the new PUI test site, I *think* maybe this is something 
that is just not working now that will be fixed when it gets released? 
Could anyone confirm this?
 
I am in the midst of designing a project for students that is supposed to 
start in a week ? I?d like to have them create agent records, but not if 
it won?t display correctly?

Best,
Annie 
 
--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu
718-409-7228
 
 _______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/5c7e20a2/attachment.html>

From dhale at jhu.edu  Thu Feb  2 17:03:35 2017
From: dhale at jhu.edu (Dawn Hale)
Date: Thu, 2 Feb 2017 22:03:35 +0000
Subject: [Archivesspace_Users_Group] Unsubscribe
Message-ID: <51ed7ed685334903addad90ed2c6da99@ESGEBEX15.win.ad.jhu.edu>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/d07a1b3d/attachment.html>

From robin_wendler at harvard.edu  Thu Feb  2 17:36:30 2017
From: robin_wendler at harvard.edu (Wendler, Robin King)
Date: Thu, 2 Feb 2017 22:36:30 +0000
Subject: [Archivesspace_Users_Group] error saving an Archival Object
In-Reply-To: <CO1PR05MB3295F7D148E11A72C12BEBBE64C0@CO1PR05MB329.namprd05.prod.outlook.com>
References: <DM2PR07MB1563E888DE772B80D4C06D959E4C0@DM2PR07MB1563.namprd07.prod.outlook.com>,
 <CO1PR05MB3295F7D148E11A72C12BEBBE64C0@CO1PR05MB329.namprd05.prod.outlook.com>
Message-ID: <DM2PR07MB1563E6D8194FA3DC0CD822159E4C0@DM2PR07MB1563.namprd07.prod.outlook.com>


Thanks, Noah, much appreciated. I can follow up from that. Apologies for not finding the issue in JIRA -- I tried!

Robin

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Noah Huffman <noah.huffman at duke.edu>
Sent: Thursday, February 2, 2017 4:37 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] error saving an Archival Object


Robin,



Here's an unresolved JIRA issue describing this problem: https://archivesspace.atlassian.net/browse/AR-1326<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1326&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=JKUSUWdXrLBGP_rNc_JtcJNO9wvGRzWSZ2uoZzcT59w&m=fgOWxSWuXz7QmRfUg2ooThQwGDM4LH_Nf25X0cMflps&s=U5qNy3vSM3JnoAjrjHnZapxkY0Hz0_nirOPpC8-gMKw&e=>



It tends to happen when you try to edit an archival object record that has been transferred from another resource record.



As far as I know, there are a couple of fixes for this:

1.       Resequence your entire ASpace database.  To do this, shut down ASpace, modify config.rb (#AppConfig[:resequence_on_startup] = True), and restart.  Beware that resequencing a large database will take a long time, but this should prevent the same error from occurring in other records.

2.       Install this plugin that allows you to resequence only the resource record where the error occurs: https://github.com/archivesspace/resync<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_resync&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=JKUSUWdXrLBGP_rNc_JtcJNO9wvGRzWSZ2uoZzcT59w&m=fgOWxSWuXz7QmRfUg2ooThQwGDM4LH_Nf25X0cMflps&s=yy1-o5Md6WysLbA5hA4Z3zBI5c_-GMOPGuL1mTjP6bY&e=>



-Noah



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Wendler, Robin King
Sent: Thursday, February 02, 2017 3:46 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] error saving an Archival Object



Hello, ASpacers,

         When saving the archival object below, changed only by adding a single space preceding "Tours" in the title, we get the following error message:



[cid:image001.png at 01D27D70.E6CB7BB0]



The same error usually occurs if we try to change other archival object records attached to this resource record, but not always. One I was able to change, but received the error when I tried to change it back. Another I could change and change back without encountering the error. The resource record itself can be changed.  Any ideas about why this is happening and what we can do to clear it up?



Thanks for your thoughts,

Robin



Robin Wendler

Library Technology Services

Harvard University

90 Mt. Auburn St.

Cambridge, MA 02138

617-495-3724

r_wendler at harvard.edu<mailto:r_wendler at harvard.edu>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/cf46bebc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 116837 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170202/cf46bebc/attachment.png>

From atummino at sunymaritime.edu  Fri Feb  3 09:48:46 2017
From: atummino at sunymaritime.edu (Tummino, Annie)
Date: Fri, 3 Feb 2017 14:48:46 +0000
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
Message-ID: <874ecaaf44af4fb49165411a7379fa6a@EX02.sunymaritime.edu>

Hello everyone:

I have a large collection of files that are physically organized by an ID number present in the records, but would make more sense intellectually to be displayed in alphabetical order.

Using rapid data entry for file level description, I'd like to enter the files based on how they are organized physically in the boxes, but then then re-sort the list alphabetically by title. Is this possible? The only re-ordering options I see are dragging and dropping individually.

Am I missing anything?

Annie


--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>
718-409-7228

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170203/42f0f316/attachment.html>

From mark.custer at yale.edu  Fri Feb  3 10:00:44 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Fri, 3 Feb 2017 15:00:44 +0000
Subject: [Archivesspace_Users_Group] Agent Records Associated
	with	Archival	Objects
In-Reply-To: <OFD546FE1D.8C9096EE-ON852580BB.0076887A-852580BB.0077B732@AUSTENRIGGS.NET>
References: <870431a184564f85b19614cb95e10cb3@EX02.sunymaritime.edu>
 <OFD546FE1D.8C9096EE-ON852580BB.0076887A-852580BB.0077B732@AUSTENRIGGS.NET>
Message-ID: <CY1PR08MB13108FDCA8988DAB66B8827D8C4F0@CY1PR08MB1310.namprd08.prod.outlook.com>

Dear Annie and Gregory,

You're correct that this is how the current PUI works.

The redesign is still under way, but it's due for its beta / candidate release at the end of March, with a production-ready release planned for the end of June.  With the new PUI, any record that's linked to an Agent record will display on that Agent's landing page.  Here's an example (although note that the "archival object" results right now are being doubled, but that should be fixed before the March release, and in this example there would be just 3 search results, not 5):

http://pui.hudmol.com/agents/people/113

All that said, it's possible that someone using the current PUI already has a plugin solution for this issue, but I'm personally not aware of one.  If so, that would be the ideal scenario, since you could get those search results showing up immediately on your current site.

All my best,

Mark


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gregory.Farr at AustenRiggs.net
Sent: Thursday, 02 February, 2017 4:48 PM
To: Archivesspace Users Group
Cc: archivesspace_users_group-bounces at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Agent Records Associated with Archival Objects

Hello,

>From what I understand working with AS, agent records only link back to 'collections' if the agents name is included in the top record of the collection that denotes all the finding aid data, etc.. If this is in fact true, it seems like a shortcoming, since it would be ideal to see all the records created by or associated with the agent when one enters an agent record based on the agent being linked to such records. I have agents linked with most of the archival and digital object records I have created, and none of this information shows up on the PUI ... only the collection the agent is related to when the agent, again, is additionally linked to the top collection record.

I am responding because I would like to see it otherwise if possible.

Best regards,
Greg


Gregory D. Farr, MLIS, CA
Librarian/Archivist
Erikson Institute for Education and Research
The Austen Riggs Center
25 Main Street
Stockbridge, MA  01262
Phone: (413) 931-5259  FAX (413) 298-4020
gregory.farr at austenriggs.net<mailto:gregory.farr at austenriggs.net>



From:        "Tummino, Annie" <atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>>
To:        Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>,
Date:        02/02/2017 04:07 PM
Subject:        [Archivesspace_Users_Group] Agent Records Associated with Archival        Objects
Sent by:        archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>
________________________________



Hello,

Apologies if this has already been addressed.

I am working on a collection that gets heavy use by genealogists. I am weighing out including names within the archival description for files versus creating agent records and linking them to the files. However, in this test, I noticed that agents associated with archival objects are not linking back to the collection on the public interface:

http://sunymaritimearchives.libraryhost.com/agents/26?agent_type=agent_person<https://urldefense.proofpoint.com/v2/url?u=http-3A__sunymaritimearchives.libraryhost.com_agents_26-3Fagent-5Ftype-3Dagent-5Fperson&d=CwMFAw&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=BaU44LyIqtU9tMWZDm7v-QV0OK8zv6XabGexG4TuQIc&s=0Qv_l3gMpjjeO4iDxFzqSC4RZxEHeTEST8cZrAHdHd4&e=>

Under Related Collections it says No Records.

Based on perusing the new PUI test site, I *think* maybe this is something that is just not working now that will be fixed when it gets released? Could anyone confirm this?

I am in the midst of designing a project for students that is supposed to start in a week - I'd like to have them create agent records, but not if it won't display correctly?

Best,
Annie

--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>
718-409-7228

 _______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMFAw&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=BaU44LyIqtU9tMWZDm7v-QV0OK8zv6XabGexG4TuQIc&s=3A-CyXsaGk9Uemls4CudcbxZCCUry_JjTBedL5Df62A&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170203/6e668aa4/attachment.html>

From j at minorscience.com  Fri Feb  3 10:37:33 2017
From: j at minorscience.com (Jason Loeffler)
Date: Fri, 3 Feb 2017 15:37:33 +0000 (UTC)
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
In-Reply-To: <874ecaaf44af4fb49165411a7379fa6a@EX02.sunymaritime.edu>
References: <874ecaaf44af4fb49165411a7379fa6a@EX02.sunymaritime.edu>
Message-ID: <E0903B9C708FD3BF.4B75503E-772B-437D-A2FF-5E4726507521@mail.outlook.com>

There are presently no alphanumeric sorting options though it seems like this would be a fairly common criteria for lists.?There is a discussion on this matter here:https://archivesspace.atlassian.net/browse/AR-1056
-- 
Jason Loeffler
Technology Consultant |?The American Academy in Rome


		_____________________________
From: Tummino, Annie <atummino at sunymaritime.edu>
Sent: Friday, February 3, 2017 08:48
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
To:  <archivesspace_users_group at lyralists.lyrasis.org>




Hello everyone:

?

I have a large collection of files that are physically organized by an ID number present in the records, but would make more sense intellectually to be displayed in alphabetical order.

?

Using rapid data entry for file level description, I?d like to enter the files based on how they are organized physically in the boxes, but then then re-sort the list alphabetically by title. Is this possible? The only re-ordering options I see are dragging and dropping individually. 

?

Am I missing anything?

?

Annie

?

?

--

Annie Tummino

Archivist & Scholarly Communication Librarian

SUNY Maritime College

atummino at sunymaritime.edu

718-409-7228

?


	
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170203/b506a724/attachment.html>

From atummino at sunymaritime.edu  Fri Feb  3 10:43:55 2017
From: atummino at sunymaritime.edu (Tummino, Annie)
Date: Fri, 3 Feb 2017 15:43:55 +0000
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
In-Reply-To: <E0903B9C708FD3BF.4B75503E-772B-437D-A2FF-5E4726507521@mail.outlook.com>
References: <874ecaaf44af4fb49165411a7379fa6a@EX02.sunymaritime.edu>
 <E0903B9C708FD3BF.4B75503E-772B-437D-A2FF-5E4726507521@mail.outlook.com>
Message-ID: <e63d872785bf491bbc6bde455272dc13@EX02.sunymaritime.edu>

Thanks Jason. To me this is a key aspect of being able to implement MPLP in a way that is still user-friendly, and distinguishing between physical and intellectual arrangements (i.e. they shouldn?t have to be the same). I hope this is considered for future updates.

Best,
Annie

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler
Sent: Friday, February 03, 2017 10:38 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Sorting files alphabetically?

There are presently no alphanumeric sorting options though it seems like this would be a fairly common criteria for lists.
There is a discussion on this matter here:
https://archivesspace.atlassian.net/browse/AR-1056

--
Jason Loeffler
Technology Consultant | The American Academy in Rome

_____________________________
From: Tummino, Annie <atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>>
Sent: Friday, February 3, 2017 08:48
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
To: <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>

Hello everyone:

I have a large collection of files that are physically organized by an ID number present in the records, but would make more sense intellectually to be displayed in alphabetical order.

Using rapid data entry for file level description, I?d like to enter the files based on how they are organized physically in the boxes, but then then re-sort the list alphabetically by title. Is this possible? The only re-ordering options I see are dragging and dropping individually.

Am I missing anything?

Annie


--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>
718-409-7228


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170203/5780fed5/attachment.html>

From mark.custer at yale.edu  Fri Feb  3 13:06:05 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Fri, 3 Feb 2017 18:06:05 +0000
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
In-Reply-To: <e63d872785bf491bbc6bde455272dc13@EX02.sunymaritime.edu>
References: <874ecaaf44af4fb49165411a7379fa6a@EX02.sunymaritime.edu>
 <E0903B9C708FD3BF.4B75503E-772B-437D-A2FF-5E4726507521@mail.outlook.com>
 <e63d872785bf491bbc6bde455272dc13@EX02.sunymaritime.edu>
Message-ID: <CY1PR08MB131009578CFE7E3BC74C39A98C4F0@CY1PR08MB1310.namprd08.prod.outlook.com>

Annie,

This probably isn?t very helpful, but so far I?ve only done this type of sorting outside of ArchivesSpace (with regular EAD-to-EAD XSLT transformations, which was helpful when I needed to ignore initial articles in the unit titles, as well as converting an EAD file to an Excel file, sorting in Excel, and then converting that file back to EAD, as demoed here: https://youtu.be/-cFUZsyykr8 ).  There?s a lot to consider with different sort options, especially if different languages are in the mix, but I hope that sorting will be part of ArchivesSpace staff interface in the future.  And I assume that a sorting feature will be considered when updating how the Rapid Data Entry feature works.

I?d also love to know if anyone has examples of how to do this with the ArchivesSpace API.  I?ve been meaning to come up with something to do that, but haven?t had a chance to experiment with anything yet, though I?d assume, for example, that you could write something to pass in an archival object ID, and then sort all of its immediate children alphabetically, by normalized date values, etc.  That?d be pretty handy, too, especially if you could review the sort order before committing to it!

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tummino, Annie
Sent: Friday, 03 February, 2017 10:44 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Sorting files alphabetically?

Thanks Jason. To me this is a key aspect of being able to implement MPLP in a way that is still user-friendly, and distinguishing between physical and intellectual arrangements (i.e. they shouldn?t have to be the same). I hope this is considered for future updates.

Best,
Annie

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler
Sent: Friday, February 03, 2017 10:38 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Sorting files alphabetically?

There are presently no alphanumeric sorting options though it seems like this would be a fairly common criteria for lists.
There is a discussion on this matter here:
https://archivesspace.atlassian.net/browse/AR-1056<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1056&d=CwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=uVFLBqqKztjJT2jigmzktEy5xOWFqiQWSqPkN1YACAI&s=Boz9cx596Tqe2K1AQH4rsaJF3TODJPEh1h4zsUM7eI0&e=>

--
Jason Loeffler
Technology Consultant | The American Academy in Rome

_____________________________
From: Tummino, Annie <atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>>
Sent: Friday, February 3, 2017 08:48
Subject: [Archivesspace_Users_Group] Sorting files alphabetically?
To: <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Hello everyone:

I have a large collection of files that are physically organized by an ID number present in the records, but would make more sense intellectually to be displayed in alphabetical order.

Using rapid data entry for file level description, I?d like to enter the files based on how they are organized physically in the boxes, but then then re-sort the list alphabetically by title. Is this possible? The only re-ordering options I see are dragging and dropping individually.

Am I missing anything?

Annie


--
Annie Tummino
Archivist & Scholarly Communication Librarian
SUNY Maritime College
atummino at sunymaritime.edu<mailto:atummino at sunymaritime.edu>
718-409-7228


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170203/f75e85e8/attachment.html>

From Gregory.Farr at AustenRiggs.net  Wed Feb  8 14:44:40 2017
From: Gregory.Farr at AustenRiggs.net (Gregory.Farr at AustenRiggs.net)
Date: Wed, 8 Feb 2017 14:44:40 -0500
Subject: [Archivesspace_Users_Group] Subject and Agent Records
	Associated with Archival Digital Objects
In-Reply-To: <CY1PR08MB13108FDCA8988DAB66B8827D8C4F0@CY1PR08MB1310.namprd08.prod.outlook.com>
References: <870431a184564f85b19614cb95e10cb3@EX02.sunymaritime.edu>
 <OFD546FE1D.8C9096EE-ON852580BB.0076887A-852580BB.0077B732@AUSTENRIGGS.NET>
 <CY1PR08MB13108FDCA8988DAB66B8827D8C4F0@CY1PR08MB1310.namprd08.prod.outlook.com>
Message-ID: <OF19E8A48C.F8EB87A9-ON852580C1.006B4CDA-852580C1.006C75EF@AUSTENRIGGS.NET>

Greetings,

I have a quick question, which perhaps someone could help me with. I've 
been successful in importing digital objects using a csv file, but I am 
wondering if there is a way to include more than just one agent and/or 
more than one subject in the record description. I've tried to find a way 
to include multiple agents and/or multiple subjects, but with no luck. I 
wonder if anyone might know of a solution?


Many thanks,
Greg


Gregory D. Farr, MLIS, CA
Librarian/Archivist
Erikson Institute for Education and Research
The Austen Riggs Center
25 Main Street
Stockbridge, MA  01262
Phone: (413) 931-5259  FAX (413) 298-4020
gregory.farr at austenriggs.net



From:   "Custer, Mark" <mark.custer at yale.edu>
To:     Archivesspace Users Group 
<archivesspace_users_group at lyralists.lyrasis.org>, 
Cc:     "archivesspace_users_group-bounces at lyralists.lyrasis.org" 
<archivesspace_users_group-bounces at lyralists.lyrasis.org>
Date:   02/03/2017 10:00 AM
Subject:        Re: [Archivesspace_Users_Group] Agent Records Associated 
with    Archival        Objects
Sent by:        archivesspace_users_group-bounces at lyralists.lyrasis.org



Dear Annie and Gregory,
 
You?re correct that this is how the current PUI works.
 
The redesign is still under way, but it?s due for its beta / candidate 
release at the end of March, with a production-ready release planned for 
the end of June.  With the new PUI, any record that?s linked to an Agent 
record will display on that Agent?s landing page.  Here?s an example 
(although note that the ?archival object? results right now are being 
doubled, but that should be fixed before the March release, and in this 
example there would be just 3 search results, not 5):
 
http://pui.hudmol.com/agents/people/113
 
All that said, it?s possible that someone using the current PUI already 
has a plugin solution for this issue, but I?m personally not aware of one. 
 If so, that would be the ideal scenario, since you could get those search 
results showing up immediately on your current site.
 
All my best,
 
Mark
 
 
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [
mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf 
Of Gregory.Farr at AustenRiggs.net
Sent: Thursday, 02 February, 2017 4:48 PM
To: Archivesspace Users Group
Cc: archivesspace_users_group-bounces at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Agent Records Associated with 
Archival Objects
 
Hello, 

>From what I understand working with AS, agent records only link back to 
'collections' if the agents name is included in the top record of the 
collection that denotes all the finding aid data, etc.. If this is in fact 
true, it seems like a shortcoming, since it would be ideal to see all the 
records created by or associated with the agent when one enters an agent 
record based on the agent being linked to such records. I have agents 
linked with most of the archival and digital object records I have 
created, and none of this information shows up on the PUI ... only the 
collection the agent is related to when the agent, again, is additionally 
linked to the top collection record. 

I am responding because I would like to see it otherwise if possible. 

Best regards, 
Greg 


Gregory D. Farr, MLIS, CA
Librarian/Archivist
Erikson Institute for Education and Research
The Austen Riggs Center
25 Main Street
Stockbridge, MA  01262
Phone: (413) 931-5259  FAX (413) 298-4020
gregory.farr at austenriggs.net 



From:        "Tummino, Annie" <atummino at sunymaritime.edu> 
To:        Archivesspace Users Group <
archivesspace_users_group at lyralists.lyrasis.org>, 
Date:        02/02/2017 04:07 PM 
Subject:        [Archivesspace_Users_Group] Agent Records Associated with 
Archival        Objects 
Sent by:        archivesspace_users_group-bounces at lyralists.lyrasis.org 




Hello, 
  
Apologies if this has already been addressed. 
  
I am working on a collection that gets heavy use by genealogists. I am 
weighing out including names within the archival description for files 
versus creating agent records and linking them to the files. However, in 
this test, I noticed that agents associated with archival objects are not 
linking back to the collection on the public interface: 
  
http://sunymaritimearchives.libraryhost.com/agents/26?agent_type=agent_person 

  
Under Related Collections it says No Records. 
  
Based on perusing the new PUI test site, I *think* maybe this is something 
that is just not working now that will be fixed when it gets released? 
Could anyone confirm this? 
  
I am in the midst of designing a project for students that is supposed to 
start in a week ? I?d like to have them create agent records, but not if 
it won?t display correctly?

Best,
Annie 
  
-- 
Annie Tummino 
Archivist & Scholarly Communication Librarian 
SUNY Maritime College 
atummino at sunymaritime.edu 
718-409-7228 
  
 _______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170208/f936ac36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DOtest.csv
Type: application/octet-stream
Size: 972 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170208/f936ac36/attachment.obj>

From christine.dibella at lyrasis.org  Wed Feb  8 16:13:41 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 8 Feb 2017 21:13:41 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate
	available - v1.5.3-RC2
Message-ID: <SN1PR08MB14067EC9941B2392D8470033F1420@SN1PR08MB1406.namprd08.prod.outlook.com>

Dear ArchivesSpace members,

We were able to put in a few additional fixes courtesy of some community pull requests (thanks, Steve Majewski!) and are making an additional release candidate available. V1.5.3-RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3-RC2) is now available for download and testing purposes. This minor release includes all of the bug fixes and improvements from the previous release candidate, as well as three additional bug fixes.

Please try out this release candidate as you are able over the next few days and let us know if you experience any problems. If you don't wish to download anything at this time, you can still test drive the release candidate on our test site, http://test.archivesspace.org, using the standard administrative login.

There are two ways to let us know the results of your testing:


*         If you have a JIRA account, put a comment on the relevant JIRA issue for the bug fix or feature. (If you don't already have a JIRA account, you can sign up directly from http://development.archivesspace.org<http://development.archivesspace.org/> by choosing the Create an account option on the login page.)

*         If you have feedback that spans issues, or if you'd prefer not to work in JIRA, email it directly to me.

If at all possible, please submit your feedback no later than Monday, February 13. Barring unforeseen issues, we expect the production release of 1.5.3 to come out by February 15. We expect the next major release of ArchivesSpace, 1.6.0, to come out in March.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170208/c90298bd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170208/c90298bd/attachment.jpg>

From blparker at umd.edu  Thu Feb  9 13:57:21 2017
From: blparker at umd.edu (Bria Lynn Parker)
Date: Thu, 9 Feb 2017 13:57:21 -0500
Subject: [Archivesspace_Users_Group] ArchivesSpace Vagrant
Message-ID: <CAAnq+k_OGw18K_H2Y_O2Ok_FkT7p-GPXrkiQ1DVOWnzNu-2KOg@mail.gmail.com>

Hi all,

I wanted to share a resource that one of my colleagues here at University
of Maryland put together for me - an ArchivesSpace vagrant! I thought the
community might find this to be a useful tool for testing release
candidates, plugins, customizations, or anything else!

For your use: https://github.com/brialparker/aspace-vagrant

Further instructions are in the README, but feel free to contact me with
any questions.

NYU also has a beautiful vagrant up on GitHub
<https://github.com/NYULibraries/vagrant-archivesspace> for 1.5.1 that has
some NYU-customizations

All the best,
Bria


-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blparker at umd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/7abf8e71/attachment.html>

From j at minorscience.com  Thu Feb  9 14:40:28 2017
From: j at minorscience.com (Jason Loeffler)
Date: Thu, 9 Feb 2017 14:40:28 -0500
Subject: [Archivesspace_Users_Group] GET & POST methods for terms
Message-ID: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>

Can anyone confirm whether the GET method for terms works? I'm getting 'Not
Found'. Also, is there an undocumented POST method for terms?

Thanks.

Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
jason at minorscience.com
(347) 405-0826
minorscience (Skype)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/a53c51eb/attachment.html>

From lewis at towson.edu  Thu Feb  9 14:38:03 2017
From: lewis at towson.edu (Lewis, Kylie)
Date: Thu, 9 Feb 2017 19:38:03 +0000
Subject: [Archivesspace_Users_Group] Redundant date expression issue
Message-ID: <MWHPR1201MB00459617E39C7C3F34BFF4EEDA450@MWHPR1201MB0045.namprd12.prod.outlook.com>

Good afternoon,

While exporting finished finding aids to PDFs, we noticed that the date expression field is creating a visually redundant copy of the date such as the image attached. Is there a way to remove the redundancy while being able to maintain a date expression? Or is this a case of possibly having to include the date in the title to remove the redundancy? Any tips would be greatly appreciated!


Kylie Lewis * Library Associate
Special Collections and University Archives
Towson University<https://www.towson.edu/> * 8000 York Road * Towson, Maryland,  21252-0001
t. 410-704-3389 * f. 410-704-3760
[http://webapps.towson.edu/ec/templates/images/facebook.png]<https://www.facebook.com/towsonuniversity> [http://webapps.towson.edu/ec/templates/images/twitter.png] <https://twitter.com/TowsonU>  [http://webapps.towson.edu/ec/templates/images/linkedin.png] <https://www.linkedin.com/edu/school?id=18562>  [http://webapps.towson.edu/ec/templates/images/instagram.png] <https://www.instagram.com/towsonuniversity/>

[Towson University logo]

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 Special Collections and University Archives at 410-704-2093.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 479 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 591 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 546 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 622 bytes
Desc: image004.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 1456 bytes
Desc: image005.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Redundant dates.JPG
Type: image/jpeg
Size: 22576 bytes
Desc: Redundant dates.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f3ee1d91/attachment.jpe>

From sdm7g at eservices.virginia.edu  Thu Feb  9 15:27:55 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Thu, 9 Feb 2017 20:27:55 +0000
Subject: [Archivesspace_Users_Group] Redundant date expression issue
In-Reply-To: <MWHPR1201MB00459617E39C7C3F34BFF4EEDA450@MWHPR1201MB0045.namprd12.prod.outlook.com>
References: <MWHPR1201MB00459617E39C7C3F34BFF4EEDA450@MWHPR1201MB0045.namprd12.prod.outlook.com>
Message-ID: <5A5146F2-B4BE-4082-99B2-AA2D1FC8FEE9@eservices.virginia.edu>


Try editing archivesspace/stylesheets/as-ead-pdf.xsl

It looks like this template at the end is appending comma ?,? and unitdate to the unit title in the first block, and then calling the unitdate template a second time in the next block.

If you edit one of those out, it should produce what you want.  ? Steve.


    <!-- Unittitles and all other clevel elements -->
    <xsl:template match="ead:did" mode="dsc">
        <fo:block margin-bottom="0">
            <xsl:apply-templates select="ead:unittitle"/>
            <xsl:if test="(string-length(ead:unittitle[1]) &gt; 1) and (string-length(ead:unitdate[1]) &gt; 1)">, </xsl:if>
            <xsl:apply-templates select="ead:unitdate" mode="did"/>
        </fo:block>
        <fo:block margin-bottom="4pt" margin-top="0">
            <xsl:apply-templates select="ead:repository" mode="dsc"/>
            <xsl:apply-templates select="ead:origination" mode="dsc"/>
            <xsl:apply-templates select="ead:unitdate" mode="dsc"/>
            <xsl:apply-templates select="ead:physdesc" mode="dsc"/>
            <xsl:apply-templates select="ead:physloc" mode="dsc"/>
            <xsl:apply-templates select="ead:dao" mode="dsc"/>
            <xsl:apply-templates select="ead:daogrp" mode="dsc"/>
            <xsl:apply-templates select="ead:langmaterial" mode="dsc"/>
            <xsl:apply-templates select="ead:materialspec" mode="dsc"/>
            <xsl:apply-templates select="ead:abstract" mode="dsc"/>
            <xsl:apply-templates select="ead:note" mode="dsc"/>
        </fo:block>
    </xsl:template>



On Feb 9, 2017, at 2:43 PM, Lewis, Kylie <lewis at towson.edu<mailto:lewis at towson.edu>> wrote:

Good afternoon,

While exporting finished finding aids to PDFs, we noticed that the date expression field is creating a visually redundant copy of the date such as the image attached. Is there a way to remove the redundancy while being able to maintain a date expression? Or is this a case of possibly having to include the date in the title to remove the redundancy? Any tips would be greatly appreciated!


Kylie Lewis ? Library Associate
Special Collections and University Archives
Towson University<https://www.towson.edu/> ? 8000 York Road ? Towson, Maryland,  21252-0001
t. 410-704-3389 ? f. 410-704-3760
<image001.png><https://www.facebook.com/towsonuniversity> <image002.png><https://twitter.com/TowsonU> <image003.png><https://www.linkedin.com/edu/school?id=18562> <image004.png><https://www.instagram.com/towsonuniversity/>

<image005.gif>

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 Special Collections and University Archives at 410-704-2093.

<Redundant dates.JPG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/0921046b/attachment.html>

From laney.mcglohon at lyrasis.org  Thu Feb  9 15:42:30 2017
From: laney.mcglohon at lyrasis.org (Laney McGlohon)
Date: Thu, 9 Feb 2017 20:42:30 +0000
Subject: [Archivesspace_Users_Group] Code4lib 2017 attendance
Message-ID: <AAEA7AE3-3EB7-40D1-B95A-3CC95C36706F@lyrasis.org>

Hello,

I wanted to let everyone know that I will be attending the code4lib conference in Los Angeles, CA, from March 6-9, 2017 (http://2017.code4lib.org/).  There will be a LYRASIS/ArchivesSpace table just outside the main ballroom.

I will be available there during the breakfast/registration hour, the morning and afternoon breaks, lunches, breakout sessions and immediately following daily sessions.

?         Tues   8-9; 10:00-10:15; 12:00-1:00; 3:00-3:40
?         Wed   8-9, 10:55-11:05; 12:05-1:00; 3:00-3:45
?         Thurs  8-9;  10:00-10:10

I look forward to talking with members of the community and getting to meet with you face-to-face.  Please come by to say hello, talk about your ArchivesSpace installations, ask questions about the future of the ArchivesSpace program or feel free to contact me if you would like to set up a separate meeting.

Laney McGlohon
ArchivesSpace Tech Lead
laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>
800.999.8558 x2927
laneymcglohon Skype

[cid:image001.jpg at 01D282EB.1F50A530]

Ask me about the Catalyst Fund<http://www.lyrasis.org/membership/Pages/Catalyst-Fund.aspx> - $100,000 to fund new ideas in YOUR institution!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/24fa6bc2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6685 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/24fa6bc2/attachment.jpg>

From james at hudmol.com  Thu Feb  9 17:40:59 2017
From: james at hudmol.com (James Bullen)
Date: Fri, 10 Feb 2017 09:40:59 +1100
Subject: [Archivesspace_Users_Group] GET & POST methods for terms
In-Reply-To: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>
References: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>
Message-ID: <6947B9F4-AE12-41B7-9939-7DB3BA030B54@hudmol.com>


Hi Jason,

There is a GET /terms endpoint. It does a search and takes a q=.

There is no GET /terms/:id - I guess this is the one that?s giving you a Not Found.

And there is no POST /terms.

Here?s the controller:
https://github.com/archivesspace/archivesspace/blob/master/backend/app/controllers/term.rb

Terms aren?t really first order objects (they get managed via their parent object), so I?m not sure why they have a uri. For example:


/terms q=Audio
{
  "first_page": 1,
  "last_page": 1,
  "this_page": 1,
  "results":
  [
    {
      "lock_version": 0,
      "term": "Audio",
      "created_by": "admin",
      "last_modified_by": "admin",
      "create_time": "2017-02-07T05:34:29Z",
      "system_mtime": "2017-02-07T05:34:29Z",
      "user_mtime": "2017-02-07T05:34:29Z",
      "term_type": "genre_form",
      "jsonmodel_type": "term",
      "uri": "/terms/3",
      "vocabulary": "/vocabularies/1"
    }
  ]
}

You see it has a uri (/terms/3), but that is a bit of a lie because there is no corresponding endpoint. There could well be a good reason for this, but I?m not aware of it.


Cheers,
James


> On Feb 10, 2017, at 6:40 AM, Jason Loeffler <j at minorscience.com> wrote:
> 
> Can anyone confirm whether the GET method for terms works? I'm getting 'Not Found'. Also, is there an undocumented POST method for terms?
> 
> Thanks.
> 
> Jason Loeffler
> Technology Consultant | The American Academy in Rome
> Minor Science | Application Development & Metadata Strategy
> Brooklyn, New York
> jason at minorscience.com <mailto:jason at minorscience.com>
> (347) 405-0826
> minorscience (Skype)
> 
> 
> !DSPAM:589cc60444364107784971! _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:589cc60444364107784971!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/4883f90e/attachment.html>

From j at minorscience.com  Thu Feb  9 18:05:45 2017
From: j at minorscience.com (Jason Loeffler)
Date: Thu, 9 Feb 2017 18:05:45 -0500
Subject: [Archivesspace_Users_Group] GET & POST methods for terms
In-Reply-To: <6947B9F4-AE12-41B7-9939-7DB3BA030B54@hudmol.com>
References: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>
 <6947B9F4-AE12-41B7-9939-7DB3BA030B54@hudmol.com>
Message-ID: <CAP4gJsW1J9FT6KorxrSDkOPOnvoXK0Z_N3mNKEVUKFuHSSUZWg@mail.gmail.com>

Thanks, James. Looking at the docs again, I now see my misunderstanding.

term.*.uri is indeed misleading. Could be a mnemonic for the term database
identifier (term.id) or otherwise a development artifact.

So I take it 1) terms can't be updated by conventional means (i.e. the API)
and 2) my primary alternative is to issue database queries in order to
perform bulk updates to a set of terms?

JL


On Thu, Feb 9, 2017 at 5:40 PM, James Bullen <james at hudmol.com> wrote:

>
> Hi Jason,
>
> There is a GET /terms endpoint. It does a search and takes a q=.
>
> There is no GET /terms/:id - I guess this is the one that?s giving you a
> Not Found.
>
> And there is no POST /terms.
>
> Here?s the controller:
> https://github.com/archivesspace/archivesspace/blob/master/backend/app/
> controllers/term.rb
>
> Terms aren?t really first order objects (they get managed via their parent
> object), so I?m not sure why they have a uri. For example:
>
>
> /terms q=Audio
> {
>   "first_page": 1,
>   "last_page": 1,
>   "this_page": 1,
>   "results":
>   [
>     {
>       "lock_version": 0,
>       "term": "Audio",
>       "created_by": "admin",
>       "last_modified_by": "admin",
>       "create_time": "2017-02-07T05:34:29Z",
>       "system_mtime": "2017-02-07T05:34:29Z",
>       "user_mtime": "2017-02-07T05:34:29Z",
>       "term_type": "genre_form",
>       "jsonmodel_type": "term",
>       "uri": "/terms/3",
>       "vocabulary": "/vocabularies/1"
>     }
>   ]
> }
>
> You see it has a uri (/terms/3), but that is a bit of a lie because there
> is no corresponding endpoint. There could well be a good reason for this,
> but I?m not aware of it.
>
>
> Cheers,
> James
>
>
> On Feb 10, 2017, at 6:40 AM, Jason Loeffler <j at minorscience.com> wrote:
>
> Can anyone confirm whether the GET method for terms works? I'm getting
> 'Not Found'. Also, is there an undocumented POST method for terms?
>
> Thanks.
>
> Jason Loeffler
> Technology Consultant | The American Academy in Rome
> Minor Science | Application Development & Metadata Strategy
> Brooklyn, New York
> jason at minorscience.com
> (347) 405-0826
> minorscience (Skype)
>
>
> !DSPAM:589cc60444364107784971! ______________________________
> _________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
> !DSPAM:589cc60444364107784971!
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170209/f57e5b4d/attachment.html>

From james at hudmol.com  Thu Feb  9 18:24:57 2017
From: james at hudmol.com (James Bullen)
Date: Fri, 10 Feb 2017 10:24:57 +1100
Subject: [Archivesspace_Users_Group] GET & POST methods for terms
In-Reply-To: <CAP4gJsW1J9FT6KorxrSDkOPOnvoXK0Z_N3mNKEVUKFuHSSUZWg@mail.gmail.com>
References: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>
 <6947B9F4-AE12-41B7-9939-7DB3BA030B54@hudmol.com>
 <CAP4gJsW1J9FT6KorxrSDkOPOnvoXK0Z_N3mNKEVUKFuHSSUZWg@mail.gmail.com>
Message-ID: <892A77AE-2E3A-4087-87D9-100B52CEC6C5@hudmol.com>


Hi Jason,

As I said, terms are managed via their parent records? endpoints. So, for example:

POST /subjects
{
  "source": "local",
  "terms":
  [
    {
      "term": "Sausages",
      "term_type": "cultural_context",
      "vocabulary": "/vocabularies/1"
    }
  ],
  "vocabulary": "/vocabularies/1?
}

Will return something like:

{
  "status": "Created",
  "id": 4,
  "lock_version": 0,
  "stale": true,
  "uri": "/subjects/4",
  "warnings": []
}

And then, you can do:

/terms q=Saus
{
  "first_page": 1,
  "last_page": 1,
  "this_page": 1,
  "results":
  [
    {
      "lock_version": 0,
      "term": "Sausages",
      "created_by": "admin",
      "last_modified_by": "admin",
      "create_time": "2017-02-09T23:16:24Z",
      "system_mtime": "2017-02-09T23:16:24Z",
      "user_mtime": "2017-02-09T23:16:24Z",
      "term_type": "cultural_context",
      "jsonmodel_type": "term",
      "uri": "/terms/5",
      "vocabulary": "/vocabularies/1"
    }
  ]
}

And, yes, the id in the uri is the db id, so:

mysql> select id, vocab_id, term, term_type_id from term where id=5;
+----+----------+----------+--------------+
| id | vocab_id | term     | term_type_id |
+----+----------+----------+--------------+
|  5 |        1 | Sausages |         1267 |
+----+----------+----------+--------------+
1 row in set (0.00 sec)


I you wanted to do bulk updates to terms you could do it via the db, or write an endpoint to do it.

Hope that helps.


Cheers,
James



> On Feb 10, 2017, at 10:05 AM, Jason Loeffler <j at minorscience.com> wrote:
> 
> Thanks, James. Looking at the docs again, I now see my misunderstanding. 
> 
> term.*.uri is indeed misleading. Could be a mnemonic for the term database identifier (term.id <http://term.id/>) or otherwise a development artifact.
> 
> So I take it 1) terms can't be updated by conventional means (i.e. the API) and 2) my primary alternative is to issue database queries in order to perform bulk updates to a set of terms? 
> 
> JL
> 
> 
> On Thu, Feb 9, 2017 at 5:40 PM, James Bullen <james at hudmol.com <mailto:james at hudmol.com>> wrote:
> 
> Hi Jason,
> 
> There is a GET /terms endpoint. It does a search and takes a q=.
> 
> There is no GET /terms/:id - I guess this is the one that?s giving you a Not Found.
> 
> And there is no POST /terms.
> 
> Here?s the controller:
> https://github.com/archivesspace/archivesspace/blob/master/backend/app/controllers/term.rb <https://github.com/archivesspace/archivesspace/blob/master/backend/app/controllers/term.rb>
> 
> Terms aren?t really first order objects (they get managed via their parent object), so I?m not sure why they have a uri. For example:
> 
> 
> /terms q=Audio
> {
>   "first_page": 1,
>   "last_page": 1,
>   "this_page": 1,
>   "results":
>   [
>     {
>       "lock_version": 0,
>       "term": "Audio",
>       "created_by": "admin",
>       "last_modified_by": "admin",
>       "create_time": "2017-02-07T05:34:29Z",
>       "system_mtime": "2017-02-07T05:34:29Z",
>       "user_mtime": "2017-02-07T05:34:29Z",
>       "term_type": "genre_form",
>       "jsonmodel_type": "term",
>       "uri": "/terms/3",
>       "vocabulary": "/vocabularies/1"
>     }
>   ]
> }
> 
> You see it has a uri (/terms/3), but that is a bit of a lie because there is no corresponding endpoint. There could well be a good reason for this, but I?m not aware of it.
> 
> 
> Cheers,
> James
> 
> 
>> On Feb 10, 2017, at 6:40 AM, Jason Loeffler <j at minorscience.com <mailto:j at minorscience.com>> wrote:
>> 
>> Can anyone confirm whether the GET method for terms works? I'm getting 'Not Found'. Also, is there an undocumented POST method for terms?
>> 
>> Thanks.
>> 
>> Jason Loeffler
>> Technology Consultant | The American Academy in Rome
>> Minor Science | Application Development & Metadata Strategy
>> Brooklyn, New York
>> jason at minorscience.com <mailto:jason at minorscience.com>
>> (347) 405-0826 <tel:(347)%20405-0826>
>> minorscience (Skype)
>> 
>> 
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>> 
>> 
>> !DSPAM:589cc60444364107784971!
> 
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:589cf5e8158171473716713! _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:589cf5e8158171473716713!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/149bc21b/attachment.html>

From j at minorscience.com  Thu Feb  9 21:16:34 2017
From: j at minorscience.com (Jason Loeffler)
Date: Fri, 10 Feb 2017 02:16:34 +0000 (UTC)
Subject: [Archivesspace_Users_Group] GET & POST methods for terms
In-Reply-To: <892A77AE-2E3A-4087-87D9-100B52CEC6C5@hudmol.com>
References: <CAP4gJsWXx-W3fXB5G4L_E=L2jYqFjCt=YSKLiU+tO-eTvK6gJQ@mail.gmail.com>
 <6947B9F4-AE12-41B7-9939-7DB3BA030B54@hudmol.com>
 <CAP4gJsW1J9FT6KorxrSDkOPOnvoXK0Z_N3mNKEVUKFuHSSUZWg@mail.gmail.com>
 <892A77AE-2E3A-4087-87D9-100B52CEC6C5@hudmol.com>
Message-ID: <75AA742E660C81F8.7898287C-2263-4AD1-ADC3-3EC703903245@mail.outlook.com>

Got it. Thanks again.?





On Thu, Feb 9, 2017 at 6:25 PM -0500, "James Bullen" <james at hudmol.com> wrote:











Hi Jason,
As I said, terms are managed via their parent records? endpoints. So, for example:
POST /subjects{??"source": "local",??"terms":??[? ??{? ? ??"term": "Sausages",? ? ??"term_type": "cultural_context",? ? ??"vocabulary": "/vocabularies/1"? ??}??],??"vocabulary": "/vocabularies/1?}
Will return something like:
{??"status": "Created",??"id": 4,??"lock_version": 0,??"stale": true,??"uri": "/subjects/4",??"warnings": []}
And then, you can do:
/terms q=Saus{??"first_page": 1,??"last_page": 1,??"this_page": 1,??"results":??[? ??{? ? ??"lock_version": 0,? ? ??"term": "Sausages",? ? ??"created_by": "admin",? ? ??"last_modified_by": "admin",? ? ??"create_time": "2017-02-09T23:16:24Z",? ? ??"system_mtime": "2017-02-09T23:16:24Z",? ? ??"user_mtime": "2017-02-09T23:16:24Z",? ? ??"term_type": "cultural_context",? ? ??"jsonmodel_type": "term",? ? ??"uri": "/terms/5",? ? ??"vocabulary": "/vocabularies/1"? ??}??]}
And, yes, the id in the uri is the db id, so:
mysql> select id, vocab_id, term, term_type_id from term where id=5;+----+----------+----------+--------------+| id | vocab_id | term?? ??| term_type_id |+----+----------+----------+--------------+|??5 |? ? ? ??1 | Sausages |?? ? ? ??1267 |+----+----------+----------+--------------+1 row in set (0.00 sec)

I you wanted to do bulk updates to terms you could do it via the db, or write an endpoint to do it.
Hope that helps.

Cheers,James


On Feb 10, 2017, at 10:05 AM, Jason Loeffler <j at minorscience.com> wrote:
Thanks, James. Looking at the docs again, I now see my misunderstanding.?
term.*.uri is indeed misleading. Could be a?mnemonic for the term database identifier (term.id) or otherwise a development artifact.
So I take it 1) terms can't be updated by conventional means (i.e. the API) and 2) my primary alternative is to issue database queries in order to perform bulk updates to a set of terms??
JL

On Thu, Feb 9, 2017 at 5:40 PM, James Bullen?<james at hudmol.com>?wrote:

Hi Jason,
There is a GET /terms endpoint. It does a search and takes a q=.
There is no GET /terms/:id - I guess this is the one that?s giving you a Not Found.
And there is no POST /terms.
Here?s the controller:https://github.com/archivesspace/archivesspace/blob/master/backend/app/controllers/term.rb
Terms aren?t really first order objects (they get managed via their parent object), so I?m not sure why they have a uri. For example:

/terms q=Audio{??"first_page": 1,??"last_page": 1,??"this_page": 1,??"results":??[? ??{? ? ??"lock_version": 0,? ? ??"term": "Audio",? ? ??"created_by": "admin",? ? ??"last_modified_by": "admin",? ? ??"create_time": "2017-02-07T05:34:29Z",? ? ??"system_mtime": "2017-02-07T05:34:29Z",? ? ??"user_mtime": "2017-02-07T05:34:29Z",? ? ??"term_type": "genre_form",? ? ??"jsonmodel_type": "term",? ? ??"uri": "/terms/3",? ? ??"vocabulary": "/vocabularies/1"? ??}??]}
You see it has a uri (/terms/3), but that is a bit of a lie because there is no corresponding endpoint. There could well be a good reason for this, but I?m not aware of it.

Cheers,James

On Feb 10, 2017, at 6:40 AM, Jason Loeffler <j at minorscience.com> wrote:
Can anyone confirm whether the GET method for terms works? I'm getting 'Not Found'. Also, is there an undocumented POST method for terms?
Thanks.
Jason LoefflerTechnology Consultant |?The American Academy in RomeMinor Science | Application Development & Metadata StrategyBrooklyn, New Yorkjason at minorscience.com(347) 405-0826minorscience (Skype)

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


!DSPAM:589cc60444364107784971!


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


!DSPAM:589cf5e8158171473716713! _______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


!DSPAM:589cf5e8158171473716713!





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/f4fe1b6d/attachment.html>

From smithkr at mit.edu  Fri Feb 10 10:10:06 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Fri, 10 Feb 2017 15:10:06 +0000
Subject: [Archivesspace_Users_Group] Redundant date expression issue -
 another solution
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01047F3987@OC11expo28.exchange.mit.edu>

Hi all,
We had the same issue here at MIT and suppressed the second date line so it only shows the Date Expression.  There are a few other customizations that we put into it (like suppressing some notes and adding an MIT specific header/footer) but you can at least copy / look at the bit that suppressed the second printed unitdate.

Available at:   https://raw.githubusercontent.com/frrrances/ASpace-style/master/as-ead-pdf.xsl

Kari

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/  @karirene69

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Thursday, February 09, 2017 3:28 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Redundant date expression issue


Try editing archivesspace/stylesheets/as-ead-pdf.xsl

It looks like this template at the end is appending comma ?,? and unitdate to the unit title in the first block, and then calling the unitdate template a second time in the next block.

If you edit one of those out, it should produce what you want.  ? Steve.


    <!-- Unittitles and all other clevel elements -->
    <xsl:template match="ead:did" mode="dsc">
        <fo:block margin-bottom="0">
            <xsl:apply-templates select="ead:unittitle"/>
            <xsl:if test="(string-length(ead:unittitle[1]) &gt; 1) and (string-length(ead:unitdate[1]) &gt; 1)">, </xsl:if>
            <xsl:apply-templates select="ead:unitdate" mode="did"/>
        </fo:block>
        <fo:block margin-bottom="4pt" margin-top="0">
            <xsl:apply-templates select="ead:repository" mode="dsc"/>
            <xsl:apply-templates select="ead:origination" mode="dsc"/>
            <xsl:apply-templates select="ead:unitdate" mode="dsc"/>
            <xsl:apply-templates select="ead:physdesc" mode="dsc"/>
            <xsl:apply-templates select="ead:physloc" mode="dsc"/>
            <xsl:apply-templates select="ead:dao" mode="dsc"/>
            <xsl:apply-templates select="ead:daogrp" mode="dsc"/>
            <xsl:apply-templates select="ead:langmaterial" mode="dsc"/>
            <xsl:apply-templates select="ead:materialspec" mode="dsc"/>
            <xsl:apply-templates select="ead:abstract" mode="dsc"/>
            <xsl:apply-templates select="ead:note" mode="dsc"/>
        </fo:block>
    </xsl:template>



On Feb 9, 2017, at 2:43 PM, Lewis, Kylie <lewis at towson.edu<mailto:lewis at towson.edu>> wrote:

Good afternoon,

While exporting finished finding aids to PDFs, we noticed that the date expression field is creating a visually redundant copy of the date such as the image attached. Is there a way to remove the redundancy while being able to maintain a date expression? Or is this a case of possibly having to include the date in the title to remove the redundancy? Any tips would be greatly appreciated!


Kylie Lewis ? Library Associate
Special Collections and University Archives
Towson University<https://www.towson.edu/> ? 8000 York Road ? Towson, Maryland,  21252-0001
t. 410-704-3389 ? f. 410-704-3760
<image001.png><https://www.facebook.com/towsonuniversity> <image002.png><https://twitter.com/TowsonU> <image003.png><https://www.linkedin.com/edu/school?id=18562> <image004.png><https://www.instagram.com/towsonuniversity/>

<image005.gif>

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 Special Collections and University Archives at 410-704-2093.

<Redundant dates.JPG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/858960d4/attachment.html>

From Alston.Cobourn at tamucc.edu  Fri Feb 10 10:42:15 2017
From: Alston.Cobourn at tamucc.edu (Cobourn, Alston)
Date: Fri, 10 Feb 2017 15:42:15 +0000
Subject: [Archivesspace_Users_Group] EAD import completed but resource,
 subject, agent records not/half created
Message-ID: <BLUPR06MB067CB9270FACBDC06546197E0440@BLUPR06MB067.namprd06.prod.outlook.com>

Dear all,

Yesterday I tested out EAD import into the AS 1.4.2 test repository of the production instance at the university to which I have recently moved.  I uploaded an EAD XML file that I had generated from the 1.5.2 AS repository at my last job.  The import says it completed successfully and the import log below seems to support that.  All the subjects and agents in the EAD are listed below the log in the New & Modified Records section, and if you click them they do link to newly created Agent and Subject records that say they are linked to no resources. 

However, if I browse Agents and Subjects none of the newly created Agents and Subjects are listed.  If I search for the newly created Agents and Subjects they are not findable.  So I have some evidence that says they were created and other evidence that says they weren't.  The resource record I intended to create is also not findable via search or browsing, so it would appear that it was not created, which I don't understand since the background job says completed.

I thought originally that perhaps this was an indexing issue, so I waited overnight but have the same results this morning.  Also, I am able to manually add subjects, agents, and resource records in AS and have them appear via search and browse immediately afterwards.  

Does anyone have thoughts as to what could be going on?

==================================================
WLU.Coll.0128_ead.xml
==================================================
1. STARTED: Reading JSON records
1. DONE: Reading JSON records
2. STARTED: Validating records and checking links
2. DONE: Validating records and checking links
3. STARTED: Evaluating record relationships
3. DONE: Evaluating record relationships
4. STARTED: Saving records: cycle 1
Created: /agents/corporate_entities/import_7e59a12f-b7de-4fb1-9527-c2560077d28a
Created: /subjects/import_4430d7be-8431-4758-9d1b-72cb8a16e982
Created: /subjects/import_f9dad788-a3a5-4b90-be77-20b661d9e3b8
Created: /subjects/import_a2c7311f-fd06-42ca-afcb-7c31b98c6442
Created: /agents/corporate_entities/import_c12b78d0-3bf4-4a66-9d13-c67de471fa44
Created: /repositories/import/resources/import_ef64de18-8bf5-4d50-ad06-8ebabda82e52
4. DONE: Saving records: cycle 1
5. STARTED: Cleaning up
5. DONE: Cleaning up



From megan.mummey at uky.edu  Fri Feb 10 13:56:44 2017
From: megan.mummey at uky.edu (Mummey, Megan)
Date: Fri, 10 Feb 2017 18:56:44 +0000
Subject: [Archivesspace_Users_Group] Exporting issues
Message-ID: <BY2PR0301MB19741966C6602E64427EC6868D440@BY2PR0301MB1974.namprd03.prod.outlook.com>

Hi all,

Has anyone else been experiencing data scrambling upon export (for both pdf and ead)? We updated to 1.5.2 in early January and are now experiencing parts of components moving around. See the example below:

A subseries exported with the title of a lower subseries. The folders are the ones for the Alice Stone Blackwell subseries, but they've exported with the subseries title of Harriet Taylor Upton.





The EAD is exporting this way too. It's happening on multiple finding aids, and is very concerning for us as an institution that uses our own public interface.

Thanks,

Megan Mummey
Collections Management Archivist
Special Collections Research Center
University of Kentucky Libraries
Margaret I. King Library
Lexington, KY  40506-0039
megan.mummey at uky.edu<mailto:Megan.mummey at uky.edu>|859.257.6942



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/db175cf1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 1.jpg
Type: image/jpeg
Size: 31503 bytes
Desc: Picture (Device Independent Bitmap) 1.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/db175cf1/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 2.jpg
Type: image/jpeg
Size: 45394 bytes
Desc: Picture (Device Independent Bitmap) 2.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/db175cf1/attachment-0001.jpg>

From noah.huffman at duke.edu  Fri Feb 10 14:06:37 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Fri, 10 Feb 2017 19:06:37 +0000
Subject: [Archivesspace_Users_Group] Exporting issues
In-Reply-To: <BY2PR0301MB19741966C6602E64427EC6868D440@BY2PR0301MB1974.namprd03.prod.outlook.com>
References: <BY2PR0301MB19741966C6602E64427EC6868D440@BY2PR0301MB1974.namprd03.prod.outlook.com>
Message-ID: <CO1PR05MB32902D49F49C594EABFE1E5E6440@CO1PR05MB329.namprd05.prod.outlook.com>

Hi Megan,

I believe this issue will be fixed in version 1.5.3 and the fix is available in the release candidates for 1.5.3.

Here is the JIRA issue: https://archivesspace.atlassian.net/browse/AR-1620

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mummey, Megan
Sent: Friday, February 10, 2017 1:57 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Exporting issues

Hi all,

Has anyone else been experiencing data scrambling upon export (for both pdf and ead)? We updated to 1.5.2 in early January and are now experiencing parts of components moving around. See the example below:

A subseries exported with the title of a lower subseries. The folders are the ones for the Alice Stone Blackwell subseries, but they've exported with the subseries title of Harriet Taylor Upton.

[cid:image001.jpg at 01D283A6.E30B63F0]

[cid:image002.jpg at 01D283A6.E30B63F0]

The EAD is exporting this way too. It's happening on multiple finding aids, and is very concerning for us as an institution that uses our own public interface.

Thanks,

Megan Mummey
Collections Management Archivist
Special Collections Research Center
University of Kentucky Libraries
Margaret I. King Library
Lexington, KY  40506-0039
megan.mummey at uky.edu<mailto:Megan.mummey at uky.edu>|859.257.6942



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/913c87ec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 31503 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/913c87ec/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 45394 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170210/913c87ec/attachment-0003.jpg>

From jteitelbaum at pabmc.net  Mon Feb 13 09:49:52 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Mon, 13 Feb 2017 09:49:52 -0500
Subject: [Archivesspace_Users_Group] Error Running Report
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D381E57@bmcmail2.PABMC.NET>

I just finished migrating from Archon to AS 1.4.2 and have moved the installation to our production server. Everything seems to be running fine, except for some of the reports. When running the DigitalObjectListReport, for example, the attached error shows up. About 12 of the reports generate a similar error. On the migration server, they ran fine. Any help would be appreciated.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170213/d6c538ee/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASReportError.rtf
Type: application/rtf
Size: 20582 bytes
Desc: ASReportError.rtf
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170213/d6c538ee/attachment.rtf>

From gmiralla at kennesaw.edu  Mon Feb 13 14:56:31 2017
From: gmiralla at kennesaw.edu (Gilberto Miralla-Flores)
Date: Mon, 13 Feb 2017 14:56:31 -0500 (EST)
Subject: [Archivesspace_Users_Group] Migrating From Archon & AT
Message-ID: <133757679.659148.1487015791053.JavaMail.zimbra@kennesaw.edu>

Hello-- 

Has anyone migrated both Archon and Archiver's Toolkit data (using the migration tools) into a single ArchivesSpace installation? We use both Archon and AT and are wondering if there are any challenges we would face if we were to attempt to migrate the two into a single AS install in order to have a central space for the two different purposes that they currently serve. 

Any input is greatly appreciated. 

Thanks, 

-G.J. Miralla-Flores 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170213/14590d0d/attachment.html>

From noah.huffman at duke.edu  Tue Feb 14 11:39:38 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 14 Feb 2017 16:39:38 +0000
Subject: [Archivesspace_Users_Group] Migrating From Archon & AT
In-Reply-To: <133757679.659148.1487015791053.JavaMail.zimbra@kennesaw.edu>
References: <133757679.659148.1487015791053.JavaMail.zimbra@kennesaw.edu>
Message-ID: <BN6PR05MB3474739928CE317EC3D2896FE6580@BN6PR05MB3474.namprd05.prod.outlook.com>

Hi G.J,

This doesn?t answer your question?but I?m curious how you use AT and Archon in tandem?  What purpose does each serve?

I?m not totally clear on what would happen if you used the migration tools for each system to migrate data into a single AS install. My hunch is that you might end up with multiple repositories in your AS instance, one for the AT data and one for the Archon data.

I?m curious if others have any experience with this problem?

-Noah

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gilberto Miralla-Flores
Sent: Monday, February 13, 2017 2:57 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Migrating From Archon & AT

Hello--

Has anyone migrated both Archon and Archiver's Toolkit data (using the migration tools) into a single ArchivesSpace installation? We use both Archon and AT and are wondering if there are any challenges we would face if we were to attempt to migrate the two into a single AS install in order to have a central space for the two different purposes that they currently serve.

Any input is greatly appreciated.

Thanks,

-G.J. Miralla-Flores

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/4d5ec38f/attachment.html>

From gmiralla at kennesaw.edu  Tue Feb 14 12:15:01 2017
From: gmiralla at kennesaw.edu (Gilberto Miralla-Flores)
Date: Tue, 14 Feb 2017 12:15:01 -0500 (EST)
Subject: [Archivesspace_Users_Group] Migrating From Archon & AT
In-Reply-To: <BN6PR05MB3474739928CE317EC3D2896FE6580@BN6PR05MB3474.namprd05.prod.outlook.com>
References: <133757679.659148.1487015791053.JavaMail.zimbra@kennesaw.edu>
 <BN6PR05MB3474739928CE317EC3D2896FE6580@BN6PR05MB3474.namprd05.prod.outlook.com>
Message-ID: <654207149.1001393.1487092501959.JavaMail.zimbra@kennesaw.edu>

Noah-- 

I wouldn't say it's being used in tandem, more like in parallel. AT is used for a type of internal-use-only information, while the Archon instance is public-facing. 

I share your hunch that it'll end up being two separate repositories. I won't know for sure until I get a chance to try it within the next few weeks, at which point I can report back the result. I was hoping to get someone's experience from here to prepare for what's ahead. 

-G.J. Miralla-Flores 


From: "Noah Huffman" <noah.huffman at duke.edu> 
To: "archivesspace users group" <archivesspace_users_group at lyralists.lyrasis.org> 
Sent: Tuesday, February 14, 2017 11:39:38 AM 
Subject: Re: [Archivesspace_Users_Group] Migrating From Archon & AT 



Hi G.J, 



This doesn?t answer your question?but I?m curious how you use AT and Archon in tandem? What purpose does each serve? 



I?m not totally clear on what would happen if you used the migration tools for each system to migrate data into a single AS install. My hunch is that you might end up with multiple repositories in your AS instance, one for the AT data and one for the Archon data. 



I?m curious if others have any experience with this problem? 



-Noah 




From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gilberto Miralla-Flores 
Sent: Monday, February 13, 2017 2:57 PM 
To: archivesspace_users_group at lyralists.lyrasis.org 
Subject: [Archivesspace_Users_Group] Migrating From Archon & AT 





Hello-- 





Has anyone migrated both Archon and Archiver's Toolkit data (using the migration tools) into a single ArchivesSpace installation? We use both Archon and AT and are wondering if there are any challenges we would face if we were to attempt to migrate the two into a single AS install in order to have a central space for the two different purposes that they currently serve. 





Any input is greatly appreciated. 





Thanks, 





-G.J. Miralla-Flores 


_______________________________________________ 
Archivesspace_Users_Group mailing list 
Archivesspace_Users_Group at lyralists.lyrasis.org 
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/087ceed1/attachment.html>

From Alston.Cobourn at tamucc.edu  Tue Feb 14 12:49:16 2017
From: Alston.Cobourn at tamucc.edu (Cobourn, Alston)
Date: Tue, 14 Feb 2017 17:49:16 +0000
Subject: [Archivesspace_Users_Group] LCSH marcxml data set
Message-ID: <DM2PR0601MB1198CDF550089A0FBEB52857E0580@DM2PR0601MB1198.namprd06.prod.outlook.com>

We are considering importing subject headings into ArchivesSpace through batch upload of marcxml. We have not yet determined if we want to use traditional LCSH or FAST.  I was able to determine how I would download bulk marcxml for different subdivision groups of FAST headings, but have not found a place to bulk download marcxml for all LCSH.  That format is not listed on the bulk download page http://id.loc.gov/download/
But I see a link to the marcxml on the webpages for individual subject headings, so it seems the data does exist in this format.  Has anyone else successfully done bulk download of marcxml for all traditional LCSH? Thanks.

Alston Cobourn
Processing and Digital Assets Archivist
Texas A&M-Corpus Christi
361-825-2300
Alston.cobourn at tamucc.edu<mailto:Alston.cobourn at tamucc.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/3bf2f9ac/attachment.html>

From CurbowJ at bvu.edu  Tue Feb 14 16:53:56 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Tue, 14 Feb 2017 21:53:56 +0000
Subject: [Archivesspace_Users_Group] Instances/Containers/Locations
Message-ID: <SN2PR05MB26556D9A5663566F407CE6D5B5580@SN2PR05MB2655.namprd05.prod.outlook.com>

Hi all,

This is a nuts-and-bolts usage question. I?ve set up top containers for all possible containers that I will use. I?ve linked some containers to a collection but did not set the locations, thinking I could do that at the very end of the processing. I also set up locations for my repository. That was actually the first thing I did after attending a training session with Aspace folks.

Now that I?m ready to assign locations to these containers, I don?t see a way to do that. I don?t see any editing function that allows for this. What am I missing?

I played around and added another ?dummy? container, and I see how it can be accomplished in that step, so does that mean that that is the ONLY time when a location can be assigned?

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu??






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/71ad5d5d/attachment.html>

From lcalahan at umn.edu  Tue Feb 14 17:01:23 2017
From: lcalahan at umn.edu (Lisa Calahan)
Date: Tue, 14 Feb 2017 16:01:23 -0600
Subject: [Archivesspace_Users_Group] Instances/Containers/Locations
In-Reply-To: <SN2PR05MB26556D9A5663566F407CE6D5B5580@SN2PR05MB2655.namprd05.prod.outlook.com>
References: <SN2PR05MB26556D9A5663566F407CE6D5B5580@SN2PR05MB2655.namprd05.prod.outlook.com>
Message-ID: <CAFfoRK5gf1krr9wfZoa+HAqj49C4Qp5igsue5hz8Sccs5TE6XQ@mail.gmail.com>

Click the Repository Settings button, select "Manage Top Containers," use
the Resource search field to search for the appropriate resource record,
select one or more containers and click the "bulk operations" button to
chose either the update bulk or single location assignment.

Hope that helps!

Lisa

On Tue, Feb 14, 2017 at 3:53 PM, Joan Curbow <CurbowJ at bvu.edu> wrote:

> Hi all,
>
>
>
> This is a nuts-and-bolts usage question. I?ve set up top containers for
> all possible containers that I will use. I?ve linked some containers to a
> collection but did not set the locations, thinking I could do that at the
> very end of the processing. I also set up locations for my repository. That
> was actually the first thing I did after attending a training session with
> Aspace folks.
>
>
>
> Now that I?m ready to assign locations to these containers, I don?t see a
> way to do that. I don?t see any editing function that allows for this. What
> am I missing?
>
>
>
> I played around and added another ?dummy? container, and I see how it can
> be accomplished in that step, so does that mean that that is the ONLY time
> when a location can be assigned?
>
>
>
> Sincerely,
>
>
>
> *Joan Curbow*
>
> Reference Librarian and Archivist
>
> Buena Vista University Library
>
> Buena Vista University
>
> 610 West Fourth Street
>
> Storm Lake, Iowa  50588
>
> 712.749.2094 <(712)%20749-2094>
>
> www.library.bvu.edu??
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/21eafcef/attachment.html>

From CurbowJ at bvu.edu  Tue Feb 14 17:12:04 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Tue, 14 Feb 2017 22:12:04 +0000
Subject: [Archivesspace_Users_Group] Instances/Containers/Locations
In-Reply-To: <CAFfoRK5gf1krr9wfZoa+HAqj49C4Qp5igsue5hz8Sccs5TE6XQ@mail.gmail.com>
References: <SN2PR05MB26556D9A5663566F407CE6D5B5580@SN2PR05MB2655.namprd05.prod.outlook.com>
 <CAFfoRK5gf1krr9wfZoa+HAqj49C4Qp5igsue5hz8Sccs5TE6XQ@mail.gmail.com>
Message-ID: <SN2PR05MB26551303CB00AAE515A91BBDB5580@SN2PR05MB2655.namprd05.prod.outlook.com>

Thanks, Lisa. That did it.

Joan

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lisa Calahan
Sent: Tuesday, February 14, 2017 4:01 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Instances/Containers/Locations

Click the Repository Settings button, select "Manage Top Containers," use the Resource search field to search for the appropriate resource record, select one or more containers and click the "bulk operations" button to chose either the update bulk or single location assignment.

Hope that helps!

Lisa

On Tue, Feb 14, 2017 at 3:53 PM, Joan Curbow <CurbowJ at bvu.edu<mailto:CurbowJ at bvu.edu>> wrote:
Hi all,

This is a nuts-and-bolts usage question. I?ve set up top containers for all possible containers that I will use. I?ve linked some containers to a collection but did not set the locations, thinking I could do that at the very end of the processing. I also set up locations for my repository. That was actually the first thing I did after attending a training session with Aspace folks.

Now that I?m ready to assign locations to these containers, I don?t see a way to do that. I don?t see any editing function that allows for this. What am I missing?

I played around and added another ?dummy? container, and I see how it can be accomplished in that step, so does that mean that that is the ONLY time when a location can be assigned?

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094<tel:(712)%20749-2094>
www.library.bvu.edu<http://www.library.bvu.edu>??







_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/22f05720/attachment.html>

From aclarkson at loyola.edu  Tue Feb 14 17:30:03 2017
From: aclarkson at loyola.edu (Anna Clarkson)
Date: Tue, 14 Feb 2017 22:30:03 +0000
Subject: [Archivesspace_Users_Group] Searching Across Repositories
Message-ID: <SN2PR01MB212836338D557F4C24D4A6E2DC580@SN2PR01MB2128.prod.exchangelabs.com>

Dear ArchivesSpace Users Group Listserv,


Has anyone figured out a way to do a federated search across multiple repositories?

The manual says 'By default, ArchivesSpace searches All Records and retrieves records for the active repository only.'


I noticed someone posted on this topic last April but I did not see any replies.   Looking to save time. Thanks for any information.


Kind regards,


Anna


Anna Clarkson
Head of Archives & Special Collections
Loyola ? Notre Dame Library
200   Winston Avenue
Baltimore, MD 21212
(410) 617-6868



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170214/fdfa8ac1/attachment.html>

From alexanderduryee at nypl.org  Wed Feb 15 11:59:51 2017
From: alexanderduryee at nypl.org (Alexander Duryee)
Date: Wed, 15 Feb 2017 11:59:51 -0500
Subject: [Archivesspace_Users_Group] Hiding Controlled Date Fields
Message-ID: <CAK5BadA0iz6=KCCZXaUDbNbvt7sXi2nioVr7t+LxTBRhCAO-NA@mail.gmail.com>

Since implementing automated date parsing in ASpace and our discovery
system, we don't have a local need for the controlled date fields in
ASpace's Date sub-form.  As such, we'd like to prevent the controlled date
fields from spawning in the data entry interface via a plug-in.

It seems that the subforms are generated by dates.crud.js, which creates
the forms upon the user selecting a date type.  I'm not quite certain how
to remove/override this bit of JavaScript via a plug-in - I tried modifying
the JS and saving the file to plugins/my-plugin/frontend/assets/, but to no
avail.  Is this the right approach to override the script's behavior, or is
there another tack I should be taking?

More ambitiously, we'd like to only show the controlled date subform to
users above a certain permission level.  We were able to implement this for
non-JS forms in the user interface (via user_can? checks), but I'm not
clear as to how this can be done for JS events.  Is this possible, and if
so, what would need to be modified?

Thanks!
--Alex

-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/405430df/attachment.html>

From christine.dibella at lyrasis.org  Wed Feb 15 12:19:13 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 15 Feb 2017 17:19:13 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace v1.5.3 released
Message-ID: <SN1PR08MB1406CB139F3FFA9FADB6FE16F15B0@SN1PR08MB1406.namprd08.prod.outlook.com>

The ArchivesSpace team is very pleased to release version 1.5.3!



You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3.



This minor release has some bug fixes, including a fix for the issue with resource components being exported in EAD in a different order from how they appear in the staff interface (https://archivesspace.atlassian.net/browse/AR-1620), as well as improvements to overall performance. It features work from our development partner, Hudson Molonglo (HM), as well as code contributions from community members Mark Cooper, Steve Majewski, Chris Fitzpatrick, Jason Loeffler, and Michael Bond. Thanks to all who contributed, participated in testing and provided the feedback that led to these improvements!


*         Please see the release page<https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3> for a listing of all the new features and bug fixes included in this release.



*         Please see the technical documentation<http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/> for information on how to upgrade your ArchivesSpace installations.


Big thanks as always to Mark Cooper, Blake Carver, and the other staff of LYRASIS' Digital Technology Services for their testing and technical support. We're also pleased to celebrate the first regular release managed by ArchivesSpace's new Tech Lead, Laney McGlohon.



Please let us know if you have questions or encounter problems executing the upgrade. The next major release of ArchivesSpace, which will include a beta of the new public interface, is expected to be available near the end of March.


Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/1596da97/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/1596da97/attachment.jpg>

From oallen at tacomacc.edu  Wed Feb 15 12:58:49 2017
From: oallen at tacomacc.edu (Allen, Odette)
Date: Wed, 15 Feb 2017 17:58:49 +0000
Subject: [Archivesspace_Users_Group] Public access of finding aids
Message-ID: <BN6PR02MB2484940E3929FD1847634270B05B0@BN6PR02MB2484.namprd02.prod.outlook.com>

I am setting up AS with the expectation that the general public will be able to digitally browse our finding aids should they wish to. In order to do this, my IT department says that I need a server with dedicated space to support the browsing, as well as server space to run the back end of AS. Is this accurate? If so, does anyone purchase server space from a reputable host? Is it horribly expensive?

Thanks!

Odette Allen
Archivist, Bldg. 7
Tacoma Community College Archive
oallen at tacomacc.edu<mailto:oallen at tacomacc.edu>; (253) 460-3990
Hours: Monday/Wednesday/Friday 8:30am - 2:30pm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/5f4bf30b/attachment.html>

From smithkr at mit.edu  Wed Feb 15 13:01:51 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Wed, 15 Feb 2017 18:01:51 +0000
Subject: [Archivesspace_Users_Group] Public access of finding aids
In-Reply-To: <BN6PR02MB2484940E3929FD1847634270B05B0@BN6PR02MB2484.namprd02.prod.outlook.com>
References: <BN6PR02MB2484940E3929FD1847634270B05B0@BN6PR02MB2484.namprd02.prod.outlook.com>
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01047FD176@OC11expo28.exchange.mit.edu>

Hi Odette,

Check the information on the ArchviesSpace.org website of Registered Service Providers.
http://archivesspace.org/registered-service-providers/current-rsps/



Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/  @karirene69

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Allen, Odette
Sent: Wednesday, February 15, 2017 12:59 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Public access of finding aids

I am setting up AS with the expectation that the general public will be able to digitally browse our finding aids should they wish to. In order to do this, my IT department says that I need a server with dedicated space to support the browsing, as well as server space to run the back end of AS. Is this accurate? If so, does anyone purchase server space from a reputable host? Is it horribly expensive?

Thanks!

Odette Allen
Archivist, Bldg. 7
Tacoma Community College Archive
oallen at tacomacc.edu<mailto:oallen at tacomacc.edu>; (253) 460-3990
Hours: Monday/Wednesday/Friday 8:30am - 2:30pm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/fa39afc3/attachment.html>

From carlos.lemus at unlv.edu  Wed Feb 15 14:08:52 2017
From: carlos.lemus at unlv.edu (Carlos Lemus)
Date: Wed, 15 Feb 2017 11:08:52 -0800
Subject: [Archivesspace_Users_Group] Enumerations Findings
Message-ID: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>

Hello,

At UNLV Special Collections, we've been working on cleaning up our
enumeration values because in many cases there were duplicates caused by
imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We
wanted to stick as close as possible to ArchivesSpace standards and decided
to make our enumeration values all lowercase seperated by an underscore and
then merge any records with incorrect enumerations into that correct value
(i.e value: linear Feet into linear_feet). We also have some custom
enumerations such as: value: oversized_box, translation: Oversized Box;
digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering
if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom
(such as the oversized_box) would come out as machine readable
oversized_box instead of using our local en.yml value (located in the local
plugin).
     This was something I found in the EAD serializer (
https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490)
and
was able to create a temporary solution of generating it , but required
altering the enumeration instead of referencing our file. I thought i'd
point it out because anyone creating custom enumerations even with a
translation in an en.yml  file would not see their change reflected in the
EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute.
Before something like Oversized Box would be export to EAD as is because
that was it's value in the enumeration. After we changed the value
correctly to oversized_box, it would export to the EAD container "type" as
is and translate to the PDF as well. With some XSLT manipulation I was able
to get it to show up as oversized box (shown in attachments). I've looked
through https://www.loc.gov/ead/tglib/elements/container.html and cannot
find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable
(Oversized Box), or does it even matter? Of course, exporting it as
Oversized Box would be easiest to translate a user friendly version to the
user.

Excuse me for the lengthy post, I'm trying to be thorough with my
explenation, but please let me know if you've come accross something
similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

*How often have I said to you that when you have eliminated the impossible,
whatever remains, however improbable, must be the truth? - Sherlock Holmes*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/91ff6f36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: enumeration_ead.PNG
Type: image/png
Size: 35440 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/91ff6f36/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: containers_enum.PNG
Type: image/png
Size: 21847 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/91ff6f36/attachment-0001.png>

From sdm7g at eservices.virginia.edu  Wed Feb 15 14:35:38 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 19:35:38 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
Message-ID: <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/25dec0f9/attachment.html>

From sustasiula at pa.gov  Wed Feb 15 14:51:43 2017
From: sustasiula at pa.gov (Stasiulatis, Suzanne)
Date: Wed, 15 Feb 2017 19:51:43 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
Message-ID: <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

[cid:image001.png at 01D2879B.058D6980]

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/cd68782b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 26000 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/cd68782b/attachment.png>

From reese.2179 at osu.edu  Wed Feb 15 14:57:33 2017
From: reese.2179 at osu.edu (Reese, Terry P.)
Date: Wed, 15 Feb 2017 19:57:33 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
Message-ID: <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

[cid:image002.png at 01D2879B.D6286D60]

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/652b44aa/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 74643 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/652b44aa/attachment.png>

From sustasiula at pa.gov  Wed Feb 15 15:12:08 2017
From: sustasiula at pa.gov (Stasiulatis, Suzanne)
Date: Wed, 15 Feb 2017 20:12:08 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
Message-ID: <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>

I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

[cid:image001.png at 01D2879D.DF7CF7D0]

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/d296d25f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 53223 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/d296d25f/attachment.png>

From reese.2179 at osu.edu  Wed Feb 15 15:17:55 2017
From: reese.2179 at osu.edu (Reese, Terry P.)
Date: Wed, 15 Feb 2017 20:17:55 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
Message-ID: <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>

I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

[cid:image002.png at 01D2879E.AE4E3830]

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/eb546a42/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 81628 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/eb546a42/attachment.png>

From lcalahan at umn.edu  Wed Feb 15 15:25:15 2017
From: lcalahan at umn.edu (Lisa Calahan)
Date: Wed, 15 Feb 2017 14:25:15 -0600
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
Message-ID: <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>

I've also received the same UTF8 error when importing legacy accession
records that have *valid* diacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu> wrote:

> I guess my question would be ? is your legacy data UTF8?  For whatever
> reason, I?ve found that historically, Archives have often used other
> charactersets when encoding their EAD files (though to be fair, I see this
> in MARC records as well; confusion between MARC8, ISO8859-1, and codepage
> 1252).  The simply solution (and this would maintain your characters) would
> be to convert the character set to UTF8.  Otherwise, even if you held on to
> these values ? they wouldn?t display in any form that you could read; and
> in fact, that is what the error message is trying to tell you.  That as a
> UTF8 value, your data is going to be gibberish, regardless of if you keep
> it or not.
>
>
>
> --tr
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Stasiulatis,
> Suzanne
> *Sent:* Wednesday, February 15, 2017 3:12 PM
>
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
>
> I totally agree that we shouldn?t have special characters if at all
> possible, but a large amount of our legacy data uses them. Especially in
> titles, staff want to use those characters as they are reflected on
> original materials.
>
>
>
> Suzanne
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Reese,
> Terry P.
> *Sent:* Wednesday, February 15, 2017 2:58 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
>
> Why would you want to retain invalid special characters?  My guess is that
> one of the reasons for this error is that invalid characters would cause
> problems with indexing for search, as well as impact display and export.  I
> would think you?d want to use the error as a flag to identify data that
> needs to be corrected.  Or am I missing something?
>
>
>
> --tr
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Stasiulatis,
> Suzanne
> *Sent:* Wednesday, February 15, 2017 2:52 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
>
> This also came up for me recently. If invalid special characters are
> present in the content titles, I get this error. I?m not sure quite how to
> adjust to accept those special characters.
>
>
>
>
>
> *Suzanne Stasiulatis *| Archivist II
> Pennsylvania Historical and Museum Commission | Pennsylvania State
> Archives
> 350 North Street | Harrisburg, PA 17120-0090
>
> Phone: 717-787-5953 <(717)%20787-5953>
>
> http://www.phmc.pa.gov
>
> sustasiula at pa.gov
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Majewski,
> Steven Dennis (sdm7g)
> *Sent:* Wednesday, February 15, 2017 2:36 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
>
>
>
>
>
> We have run into the case that some EAD attribute values are required to
> be NMTOKENs, thus no embedded spaces or other disallowed characters. We
> replaced enumerations with embedded spaces with underscores.
>
>
>
> This has only come to my attention in the last week or so, so I haven?t
> made a thorough investigation of which attributes or which enumerations
> this applies to ? just fixed them as I?ve encountered that error.
>
>
>
> So it may be intentional that it is using the non translated value.
>
> ( And I wouldn?t be surprised, if for simplicity, it may be over applying
> that rule in places where it?s not actually required. )
>
>
>
>
>
> ? Steve.
>
>
>
>
>
> On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu> wrote:
>
>
>
> Hello,
>
>
>
> At UNLV Special Collections, we've been working on cleaning up our
> enumeration values because in many cases there were duplicates caused by
> imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We
> wanted to stick as close as possible to ArchivesSpace standards and decided
> to make our enumeration values all lowercase seperated by an underscore and
> then merge any records with incorrect enumerations into that correct value
> (i.e value: linear Feet into linear_feet). We also have some custom
> enumerations such as: value: oversized_box, translation: Oversized Box;
> digital_file; Digital File
>
>
>
> After we had that set up correctly, we had some findings and was wondering
> if anyone has experienced the same things or had a standard we could use.
>
>
>
> 1. When generating PDFs and EADs the enumeration values that were custom
> (such as the oversized_box) would come out as machine readable
> oversized_box instead of using our local en.yml value (located in the local
> plugin).
>
>      This was something I found in the EAD serializer (https://github.com/
> archivesspace/archivesspace/blob/master/backend/app/
> exporters/serializers/ead.rb#L490) and was able to create a temporary
> solution of generating it , but required altering the enumeration instead
> of referencing our file. I thought i'd point it out because anyone creating
> custom enumerations even with a translation in an en.yml  file would not
> see their change reflected in the EAD export. (I've attached an image
> reflecting this) Anyone experience this?
>
>
>
> 2. Another example of this case was in the container "type" attribute.
> Before something like Oversized Box would be export to EAD as is because
> that was it's value in the enumeration. After we changed the value
> correctly to oversized_box, it would export to the EAD container "type" as
> is and translate to the PDF as well. With some XSLT manipulation I was able
> to get it to show up as oversized box (shown in attachments). I've looked
> through https://www.loc.gov/ead/tglib/elements/container.html and cannot
> find an example of a two+ attribute value.
>
>
>
> Should attributes be machine readable (i.e oversized_box), human readable
> (Oversized Box), or does it even matter? Of course, exporting it as
> Oversized Box would be easiest to translate a user friendly version to the
> user.
>
>
>
> Excuse me for the lengthy post, I'm trying to be thorough with my
> explenation, but please let me know if you've come accross something
> similar or have a finite solution.
>
>
> Carlos Lemus
>
> Application Programmer, Special Collections Technical Services
>
> University Libraries, University of Nevada, Las Vegas
>
>
>
> *How often have I said to you that when you have eliminated the
> impossible, whatever remains, however improbable, must be the truth? -
> Sherlock Holmes*
>
> <enumeration_ead.PNG><containers_enum.PNG>__________
> _____________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/39bd9cd9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 81628 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/39bd9cd9/attachment-0001.png>

From sdm7g at eservices.virginia.edu  Wed Feb 15 15:50:29 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 20:50:29 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
Message-ID: <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have valid diacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group




--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/7c8e58f5/attachment.html>

From smithkr at mit.edu  Wed Feb 15 15:54:19 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Wed, 15 Feb 2017 20:54:19 +0000
Subject: [Archivesspace_Users_Group] XLink value question for DO Instance
	File Version
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>

Hi all,
I'm having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help.

My XLink Actuate is OnLoad
XLink Show is embed

The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display to the user.

I feel like this is something I should be able to do but am having trouble even after trying several combinations of the two XLink values.

We are in version 1.4.2  so would be as happy to hear that this is a known version issue. If that's the case, what would be my ideal values for my ideal behavior in version 1.5.3?

Thanks very much!

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/  @karirene69

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/b3ec2a42/attachment.html>

From reese.2179 at osu.edu  Wed Feb 15 15:54:25 2017
From: reese.2179 at osu.edu (Reese, Terry P.)
Date: Wed, 15 Feb 2017 20:54:25 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
Message-ID: <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have valid diacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/d4ffe606/attachment.html>

From j at minorscience.com  Wed Feb 15 15:55:54 2017
From: j at minorscience.com (Jason Loeffler)
Date: Wed, 15 Feb 2017 20:55:54 +0000 (UTC)
Subject: [Archivesspace_Users_Group] Public access of finding aids
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01047FD176@OC11expo28.exchange.mit.edu>
References: <BN6PR02MB2484940E3929FD1847634270B05B0@BN6PR02MB2484.namprd02.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01047FD176@OC11expo28.exchange.mit.edu>
Message-ID: <75AA742E660C81F8.5CE59106-5B02-4513-96EB-5B26D2959277@mail.outlook.com>

Simple pricing, mostly turnkey: https://libraryhost.com/pricing





On Wed, Feb 15, 2017 at 1:01 PM -0500, "Kari R Smith" <smithkr at mit.edu> wrote:




















Hi Odette,


?


Check the information on the ArchviesSpace.org website of Registered Service Providers.


http://archivesspace.org/registered-service-providers/current-rsps/


?


?


?



Kari R. Smith


Digital Archivist and Program Head for Born-digital Archives


Institute Archives and Special Collections


Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts


617.253.5690?? smithkr at mit.edu??
http://libraries.mit.edu/archives/? @karirene69



?




From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]
On Behalf Of Allen, Odette

Sent: Wednesday, February 15, 2017 12:59 PM

To: archivesspace_users_group at lyralists.lyrasis.org

Subject: [Archivesspace_Users_Group] Public access of finding aids




?


I am setting up AS with the expectation that the general public will be able to digitally browse our finding aids should they wish to. In order to do this, my IT department says that I need a server with dedicated space to support the browsing,
 as well as server space to run the back end of AS. Is this accurate? If so, does anyone purchase server space from a reputable host? Is it horribly expensive?


?


Thanks!


?


Odette Allen


Archivist, Bldg. 7


Tacoma Community College Archive


oallen at tacomacc.edu; (253) 460-3990


Hours: Monday/Wednesday/Friday 8:30am ? 2:30pm


?








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/ad68df60/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 15 16:00:55 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 21:00:55 +0000
Subject: [Archivesspace_Users_Group] XLink value question for DO
 Instance	File Version
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>
Message-ID: <BD1DE40D-D5C2-4633-A2DC-0918B132521D@eservices.virginia.edu>


Are they full http:|https: URLs ?
( I know there?s some code that, if there is no scheme in the URLs, assumes they are file: URLs and prepends that scheme. That, and some Windows specific backslash hacks should probably be redone. )

Can you give example of the URLs and maybe a screen shot ?

? Steve.


On Feb 15, 2017, at 3:54 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Hi all,
I?m having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help.

My XLink Actuate is OnLoad
XLink Show is embed

The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display to the user.

I feel like this is something I should be able to do but am having trouble even after trying several combinations of the two XLink values.

We are in version 1.4.2  so would be as happy to hear that this is a known version issue. If that?s the case, what would be my ideal values for my ideal behavior in version 1.5.3?

Thanks very much!

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/451938bf/attachment.html>

From smithkr at mit.edu  Wed Feb 15 16:02:02 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Wed, 15 Feb 2017 21:02:02 +0000
Subject: [Archivesspace_Users_Group] XLink value question for DO
 Instance	File Version
In-Reply-To: <BD1DE40D-D5C2-4633-A2DC-0918B132521D@eservices.virginia.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>
 <BD1DE40D-D5C2-4633-A2DC-0918B132521D@eservices.virginia.edu>
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01047FDA76@OC11expo28.exchange.mit.edu>

Screenshot attached.  Yes, full URLs.

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu   http://libraries.mit.edu/archives/  @karirene69

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 4:01 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version


Are they full http:|https: URLs ?
( I know there?s some code that, if there is no scheme in the URLs, assumes they are file: URLs and prepends that scheme. That, and some Windows specific backslash hacks should probably be redone. )

Can you give example of the URLs and maybe a screen shot ?

? Steve.


On Feb 15, 2017, at 3:54 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Hi all,
I?m having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help.

My XLink Actuate is OnLoad
XLink Show is embed

The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display to the user.

I feel like this is something I should be able to do but am having trouble even after trying several combinations of the two XLink values.

We are in version 1.4.2  so would be as happy to hear that this is a known version issue. If that?s the case, what would be my ideal values for my ideal behavior in version 1.5.3?

Thanks very much!

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/9d73e190/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: URLnoLink_FileVersion.JPG
Type: image/jpeg
Size: 40040 bytes
Desc: URLnoLink_FileVersion.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/9d73e190/attachment.jpe>

From sdm7g at eservices.virginia.edu  Wed Feb 15 16:04:45 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 21:04:45 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
Message-ID: <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>

Yes, and the previous cases I?ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn?t being preserved on some other
( xml or json ) internal transform. So that might be something to look for if it?s still happening in a new use case.



On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have validdiacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/72e53b78/attachment.html>

From lcalahan at umn.edu  Wed Feb 15 16:25:30 2017
From: lcalahan at umn.edu (Lisa Calahan)
Date: Wed, 15 Feb 2017 15:25:30 -0600
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
 <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
Message-ID: <CAFfoRK41dRyQqouDZQqhhGZxKoRQ4K1iHxuUP_da4ZVv_q2v_w@mail.gmail.com>

I've attached the .csv example. I didn't test it in 1.5.3, but the bug
occurs in 1.5.2 (I know it did not occur in 1.5.1). I reported the bug on
January 17.

On Wed, Feb 15, 2017 at 3:04 PM, Majewski, Steven Dennis (sdm7g) <
sdm7g at eservices.virginia.edu> wrote:

> Yes, and the previous cases I?ve seen ( which have since been fixed ) have
> been where the document was originally parsed with correct character
> encoding, but that encoding wasn?t being preserved on some other
> ( xml or json ) internal transform. So that might be something to look for
> if it?s still happening in a new use case.
>
>
>
> On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu> wrote:
>
> I?d be interested in the same thing (a sample file).  I?m familiar with
> the tools being used, and if the data is UTF8, then you shouldn?t see this
> problem unless the import is munging the data or encoding ? which would be
> a much different problem.
>
> --tr
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Majewski,
> Steven Dennis (sdm7g)
> *Sent:* Wednesday, February 15, 2017 3:50 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
> Do you have a sample import file that fails this way ?
> Do you know if it still fail on current release ?
> ( and is bug reported on Jira ? )
>
> ? Steve.
>
>
>
> On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu> wrote:
>
> I've also received the same UTF8 error when importing legacy accession
> records that have *valid*diacritical marks in the title and/or agent name.
>
>
> Lisa
>
> On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu>
> wrote:
>
> I guess my question would be ? is your legacy data UTF8?  For whatever
> reason, I?ve found that historically, Archives have often used other
> charactersets when encoding their EAD files (though to be fair, I see this
> in MARC records as well; confusion between MARC8, ISO8859-1, and codepage
> 1252).  The simply solution (and this would maintain your characters) would
> be to convert the character set to UTF8.  Otherwise, even if you held on to
> these values ? they wouldn?t display in any form that you could read; and
> in fact, that is what the error message is trying to tell you.  That as a
> UTF8 value, your data is going to be gibberish, regardless of if you keep
> it or not.
>
> --tr
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Stasiulatis,
> Suzanne
> *Sent:* Wednesday, February 15, 2017 3:12 PM
>
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
> I totally agree that we shouldn?t have special characters if at all
> possible, but a large amount of our legacy data uses them. Especially in
> titles, staff want to use those characters as they are reflected on
> original materials.
>
> Suzanne
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Reese,
> Terry P.
> *Sent:* Wednesday, February 15, 2017 2:58 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
> Why would you want to retain invalid special characters?  My guess is that
> one of the reasons for this error is that invalid characters would cause
> problems with indexing for search, as well as impact display and export.  I
> would think you?d want to use the error as a flag to identify data that
> needs to be corrected.  Or am I missing something?
>
> --tr
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Stasiulatis,
> Suzanne
> *Sent:* Wednesday, February 15, 2017 2:52 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
> This also came up for me recently. If invalid special characters are
> present in the content titles, I get this error. I?m not sure quite how to
> adjust to accept those special characters.
>
> <image002.png>
>
> *Suzanne Stasiulatis *| Archivist II
> Pennsylvania Historical and Museum Commission | Pennsylvania State
> Archives
> 350 North Street | Harrisburg, PA 17120-0090
> Phone: 717-787-5953 <(717)%20787-5953>
> http://www.phmc.pa.gov
> sustasiula at pa.gov
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Majewski,
> Steven Dennis (sdm7g)
> *Sent:* Wednesday, February 15, 2017 2:36 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Enumerations Findings
>
>
>
> We have run into the case that some EAD attribute values are required to
> be NMTOKENs, thus no embedded spaces or other disallowed characters. We
> replaced enumerations with embedded spaces with underscores.
>
> This has only come to my attention in the last week or so, so I haven?t
> made a thorough investigation of which attributes or which enumerations
> this applies to ? just fixed them as I?ve encountered that error.
>
> So it may be intentional that it is using the non translated value.
> ( And I wouldn?t be surprised, if for simplicity, it may be over applying
> that rule in places where it?s not actually required. )
>
>
> ? Steve.
>
>
>
> On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu> wrote:
>
> Hello,
>
> At UNLV Special Collections, we've been working on cleaning up our
> enumeration values because in many cases there were duplicates caused by
> imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We
> wanted to stick as close as possible to ArchivesSpace standards and decided
> to make our enumeration values all lowercase seperated by an underscore and
> then merge any records with incorrect enumerations into that correct value
> (i.e value: linear Feet into linear_feet). We also have some custom
> enumerations such as: value: oversized_box, translation: Oversized Box;
> digital_file; Digital File
>
> After we had that set up correctly, we had some findings and was wondering
> if anyone has experienced the same things or had a standard we could use.
>
> 1. When generating PDFs and EADs the enumeration values that were custom
> (such as the oversized_box) would come out as machine readable
> oversized_box instead of using our local en.yml value (located in the local
> plugin).
>      This was something I found in the EAD serializer (https://github.com/
> archivesspace/archivesspace/blob/master/backend/app/
> exporters/serializers/ead.rb#L490) and was able to create a temporary
> solution of generating it , but required altering the enumeration instead
> of referencing our file. I thought i'd point it out because anyone creating
> custom enumerations even with a translation in an en.yml  file would not
> see their change reflected in the EAD export. (I've attached an image
> reflecting this) Anyone experience this?
>
> 2. Another example of this case was in the container "type" attribute.
> Before something like Oversized Box would be export to EAD as is because
> that was it's value in the enumeration. After we changed the value
> correctly to oversized_box, it would export to the EAD container "type" as
> is and translate to the PDF as well. With some XSLT manipulation I was able
> to get it to show up as oversized box (shown in attachments). I've looked
> through https://www.loc.gov/ead/tglib/elements/container.html and cannot
> find an example of a two+ attribute value.
>
> Should attributes be machine readable (i.e oversized_box), human readable
> (Oversized Box), or does it even matter? Of course, exporting it as
> Oversized Box would be easiest to translate a user friendly version to the
> user.
>
> Excuse me for the lengthy post, I'm trying to be thorough with my
> explenation, but please let me know if you've come accross something
> similar or have a finite solution.
>
> Carlos Lemus
> Application Programmer, Special Collections Technical Services
> University Libraries, University of Nevada, Las Vegas
>
> *How often have I said to you that when you have eliminated the
> impossible, whatever remains, however improbable, must be the truth? -
> Sherlock Holmes*
> <enumeration_ead.PNG><containers_enum.PNG>__________
> _____________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
>
> --
>
> Head of Archival Processing
>
> University of Minnesota Libraries
> Archives and Special Collections
> Elmer L. Andersen Library, Suite 315
> 222-21st Ave. S.
> Minneapolis MN 55455
>
> Phone: 612.626.2531 <(612)%20626-2531>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/7727fa37/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PAAAccessions_Feb.csv
Type: text/csv
Size: 63800 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/7727fa37/attachment.csv>

From reese.2179 at osu.edu  Wed Feb 15 16:34:28 2017
From: reese.2179 at osu.edu (Reese, Terry P.)
Date: Wed, 15 Feb 2017 21:34:28 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <CAFfoRK41dRyQqouDZQqhhGZxKoRQ4K1iHxuUP_da4ZVv_q2v_w@mail.gmail.com>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
 <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
 <CAFfoRK41dRyQqouDZQqhhGZxKoRQ4K1iHxuUP_da4ZVv_q2v_w@mail.gmail.com>
Message-ID: <EB7C977DC024F8499C24E2B2A11E83A58AB757CA@CIO-TNC-D2MBX06.osuad.osu.edu>

I don?t think the file you attached is UTF8.  I have a number of tools I use to identify encoding, and it looks like ANSI to me.  I can save it as UTF8 and the diacritics for display, don?t change, but the underlying code values most certainly do.

For example ? you your CSV file ? the following data:
New Riverside Caf?
At a binary level, the diacritic is represented as: 0x8e 0x2c

As a UTF8 file, that same diacritic would be represented as:
0xc5 0xbd

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lisa Calahan
Sent: Wednesday, February 15, 2017 4:26 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

I've attached the .csv example. I didn't test it in 1.5.3, but the bug occurs in 1.5.2 (I know it did not occur in 1.5.1). I reported the bug on January 17.

On Wed, Feb 15, 2017 at 3:04 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:
Yes, and the previous cases I?ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn?t being preserved on some other
( xml or json ) internal transform. So that might be something to look for if it?s still happening in a new use case.



On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have validdiacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531<tel:(612)%20626-2531>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/b90ef072/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 15 16:46:06 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 21:46:06 +0000
Subject: [Archivesspace_Users_Group] Enumerations Findings
In-Reply-To: <EB7C977DC024F8499C24E2B2A11E83A58AB757CA@CIO-TNC-D2MBX06.osuad.osu.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
 <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
 <CAFfoRK41dRyQqouDZQqhhGZxKoRQ4K1iHxuUP_da4ZVv_q2v_w@mail.gmail.com>
 <EB7C977DC024F8499C24E2B2A11E83A58AB757CA@CIO-TNC-D2MBX06.osuad.osu.edu>
Message-ID: <9534F88F-B685-4A7F-B625-9AD2153C222A@eservices.virginia.edu>


Same here: doesn?t look like UTF-8 to me.

Tried converting it with 'iconv -f LATIN1 -t UTF-8?
and importing it doesn?t give an character encoding error.
It does give me ?accession date : Not a valid date? error.

( This is on v1.4.2 which is what I?m running some test on now. )


? Steve.



On Feb 15, 2017, at 4:34 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I don?t think the file you attached is UTF8.  I have a number of tools I use to identify encoding, and it looks like ANSI to me.  I can save it as UTF8 and the diacritics for display, don?t change, but the underlying code values most certainly do.

For example ? you your CSV file ? the following data:
New Riverside Caf?
At a binary level, the diacritic is represented as: 0x8e 0x2c

As a UTF8 file, that same diacritic would be represented as:
0xc5 0xbd

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lisa Calahan
Sent: Wednesday, February 15, 2017 4:26 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

I've attached the .csv example. I didn't test it in 1.5.3, but the bug occurs in 1.5.2 (I know it did not occur in 1.5.1). I reported the bug on January 17.

On Wed, Feb 15, 2017 at 3:04 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:
Yes, and the previous cases I?ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn?t being preserved on some other
( xml or json ) internal transform. So that might be something to look for if it?s still happening in a new use case.



On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have validdiacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531<tel:(612)%20626-2531>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/d455c048/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 15 17:04:07 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 22:04:07 +0000
Subject: [Archivesspace_Users_Group] XLink value question for DO
 Instance	File Version
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01047FDA76@OC11expo28.exchange.mit.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>
 <BD1DE40D-D5C2-4633-A2DC-0918B132521D@eservices.virginia.edu>
 <29F559819ACA9A4FBF208407D4B63ABB01047FDA76@OC11expo28.exchange.mit.edu>
Message-ID: <F53CDAA0-977D-4C3D-943B-BC151274729D@eservices.virginia.edu>


It?s the spaces in the URL which are causing it to fail converting the string to a URI.


[2] pry(main)> u=URI( 'http://abc/def ghi xxx.pdf' )
URI::InvalidURIError: bad URI(is not URI?): http://abc/def ghi xxx.pdf
from /usr/local/var/rbenv/versions/jruby-1.7.24/lib/ruby/1.9/uri/common.rb:176:in `split'


So the template falls thru to the final case of just displaying the string, instead of the ?link_to? block above:

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/records/_file_versions.html.erb#L12


Try URL encoding the spaces as ?%20? : that should work.


I also tested on 1.4.2. That link above in current release shows the same code in the template.
I don?t know if it checks for valid URL anywhere else in current release.
Perhaps the edit form should take care of checking and encoding when saved.
Will look into this further.


? Steve.


On Feb 15, 2017, at 4:02 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Screenshot attached.  Yes, full URLs.

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 4:01 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version


Are they full http:|https: URLs ?
( I know there?s some code that, if there is no scheme in the URLs, assumes they are file: URLs and prepends that scheme. That, and some Windows specific backslash hacks should probably be redone. )

Can you give example of the URLs and maybe a screen shot ?

? Steve.


On Feb 15, 2017, at 3:54 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Hi all,
I?m having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help.

My XLink Actuate is OnLoad
XLink Show is embed

The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display to the user.

I feel like this is something I should be able to do but am having trouble even after trying several combinations of the two XLink values.

We are in version 1.4.2  so would be as happy to hear that this is a known version issue. If that?s the case, what would be my ideal values for my ideal behavior in version 1.5.3?

Thanks very much!

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

<URLnoLink_FileVersion.JPG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/3dc707ae/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 15 17:25:28 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 15 Feb 2017 22:25:28 +0000
Subject: [Archivesspace_Users_Group] JIRA issues cleanup ? [was:
	Enumerations Findings]
In-Reply-To: <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
 <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
Message-ID: <2E477697-0142-4AF3-AD06-159DB1A8E4CF@eservices.virginia.edu>


BTW: I know there?s been a recent changing of the guard, so cleanup of JIRA issues may have been neglected, but on this subject:  I believe ar-1421 and ar-647 can both be marked as closed ( and probably several others. Or is this status being tracked somewhere else?  )


https://archivesspace.atlassian.net/browse/AR-1421?jql=text%20~%20%22utf-8%22<https://archivesspace.atlassian.net/browse/AR-1421?jql=text%20~%20"utf-8">

https://archivesspace.atlassian.net/browse/AR-647?jql=text%20~%20%22utf-8%22<https://archivesspace.atlassian.net/browse/AR-647?jql=text%20~%20"utf-8">


? Steve.



On Feb 15, 2017, at 4:04 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:

Yes, and the previous cases I?ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn?t being preserved on some other
( xml or json ) internal transform. So that might be something to look for if it?s still happening in a new use case.



On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have validdiacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/6e1eca05/attachment.html>

From Alston.Cobourn at tamucc.edu  Wed Feb 15 18:04:08 2017
From: Alston.Cobourn at tamucc.edu (Cobourn, Alston)
Date: Wed, 15 Feb 2017 23:04:08 +0000
Subject: [Archivesspace_Users_Group] copyright/licensing statements in
	finding aids
Message-ID: <DM2PR0601MB11983296651B6C45D6D85CCDE05B0@DM2PR0601MB1198.namprd06.prod.outlook.com>

We would like to apply a Creative Commons license to the resource records we create in and finding aids we generate from ArchivesSpace.  Is anyone else already doing this, and if so, where are you entering that information in ArchivesSpace?



I had originally thought of putting that information somewhere in the Finding Aid Data section of Resource records (the Finding Aid Note field really would be the only possible place), but the Finding Aid Data section info does not show up in the AS public interface, and based on the wireframes, it does not appear that will change in the new PUI.  We could put it in a General Note labeled something like "Finding Aid Usage" or "Finding Aid Rights", which would show up in the PUI.



Alternately, if you are putting a copyright statement in your finding aids generated by AS, where are you entering that information?



It is my understanding that neither EAD2 nor EAD3 have field specifically designated for this kind of information.



Sincerely,



Alston Cobourn
Processing and Digital Assets Archivist
Texas A&M-Corpus Christi
Alston.cobourn at tamucc.edu<mailto:Alston.cobourn at tamucc.edu>
361-825-2300
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/fe2e5f06/attachment.html>

From mcallahan at smith.edu  Wed Feb 15 19:02:45 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Wed, 15 Feb 2017 19:02:45 -0500
Subject: [Archivesspace_Users_Group] copyright/licensing statements in
 finding aids
In-Reply-To: <DM2PR0601MB11983296651B6C45D6D85CCDE05B0@DM2PR0601MB1198.namprd06.prod.outlook.com>
References: <DM2PR0601MB11983296651B6C45D6D85CCDE05B0@DM2PR0601MB1198.namprd06.prod.outlook.com>
Message-ID: <CAH0VKbAWyTnx8=4ySrMqryMfQu6p-PhQ99cXduNTs=NXbiAZXA@mail.gmail.com>

I just wanted to say that I'm so glad that you brought this up, and that
TS-DACS has been considering adding this to the content standard for some
time now. In my opinion, there's no meaningful place for this in
ArchivesSpace right now. But since ArchivesSpace (nominally) aligns with
DACS, perhaps the first step might be a change request to DACS to include
an element in archival description to indicate how the description itself
is licensed. From there, EAD and ArchivesSpace could follow. I'd be willing
to work with you to put this together.

All best,
Maureen

On Wed, Feb 15, 2017 at 6:04 PM, Cobourn, Alston <Alston.Cobourn at tamucc.edu>
wrote:

> We would like to apply a Creative Commons license to the resource records
> we create in and finding aids we generate from ArchivesSpace.  Is anyone
> else already doing this, and if so, where are you entering that information
> in ArchivesSpace?
>
>
>
> I had originally thought of putting that information somewhere in the
> Finding Aid Data section of Resource records (the Finding Aid Note field
> really would be the only possible place), but the Finding Aid Data section
> info does not show up in the AS public interface, and based on the
> wireframes, it does not appear that will change in the new PUI.  We could
> put it in a General Note labeled something like ?Finding Aid Usage? or
> ?Finding Aid Rights?, which would show up in the PUI.
>
>
>
> Alternately, if you are putting a copyright statement in your finding aids
> generated by AS, where are you entering that information?
>
>
>
> It is my understanding that neither EAD2 nor EAD3 have field specifically
> designated for this kind of information.
>
>
>
> Sincerely,
>
>
>
> Alston Cobourn
>
> Processing and Digital Assets Archivist
>
> Texas A&M-Corpus Christi
>
> Alston.cobourn at tamucc.edu
>
> 361-825-2300 <(361)%20825-2300>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Smith College Special Collections will be closed from June through August
2017 as we move to our interim location and Neilson Library
<http://www.smith.edu/libraries/redesign> begins renovations. Although we
cannot serve researchers onsite during that time, please don't hesitate to
be in touch for remote research assistance.

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170215/24beaed9/attachment.html>

From mark.custer at yale.edu  Thu Feb 16 08:23:05 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Thu, 16 Feb 2017 13:23:05 +0000
Subject: [Archivesspace_Users_Group] copyright/licensing statements in
 finding aids
In-Reply-To: <CAH0VKbAWyTnx8=4ySrMqryMfQu6p-PhQ99cXduNTs=NXbiAZXA@mail.gmail.com>
References: <DM2PR0601MB11983296651B6C45D6D85CCDE05B0@DM2PR0601MB1198.namprd06.prod.outlook.com>
 <CAH0VKbAWyTnx8=4ySrMqryMfQu6p-PhQ99cXduNTs=NXbiAZXA@mail.gmail.com>
Message-ID: <BN3PR08MB13034A21938D131A58668F478C5A0@BN3PR08MB1303.namprd08.prod.outlook.com>

Just a quick message to note that this has also been discussed for EAD3 and will eventually be added to the schema:  https://github.com/SAA-SDT/EAD3/issues/506

So, it seems like a change request to ArchivesSpace would be pretty natural once (and, better yet, even before) it?s available in DACS and EAD3.



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maureen Callahan
Sent: Wednesday, 15 February, 2017 7:03 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] copyright/licensing statements in finding aids

I just wanted to say that I'm so glad that you brought this up, and that TS-DACS has been considering adding this to the content standard for some time now. In my opinion, there's no meaningful place for this in ArchivesSpace right now. But since ArchivesSpace (nominally) aligns with DACS, perhaps the first step might be a change request to DACS to include an element in archival description to indicate how the description itself is licensed. From there, EAD and ArchivesSpace could follow. I'd be willing to work with you to put this together.

All best,
Maureen

On Wed, Feb 15, 2017 at 6:04 PM, Cobourn, Alston <Alston.Cobourn at tamucc.edu<mailto:Alston.Cobourn at tamucc.edu>> wrote:

We would like to apply a Creative Commons license to the resource records we create in and finding aids we generate from ArchivesSpace.  Is anyone else already doing this, and if so, where are you entering that information in ArchivesSpace?



I had originally thought of putting that information somewhere in the Finding Aid Data section of Resource records (the Finding Aid Note field really would be the only possible place), but the Finding Aid Data section info does not show up in the AS public interface, and based on the wireframes, it does not appear that will change in the new PUI.  We could put it in a General Note labeled something like ?Finding Aid Usage? or ?Finding Aid Rights?, which would show up in the PUI.



Alternately, if you are putting a copyright statement in your finding aids generated by AS, where are you entering that information?



It is my understanding that neither EAD2 nor EAD3 have field specifically designated for this kind of information.



Sincerely,



Alston Cobourn
Processing and Digital Assets Archivist
Texas A&M-Corpus Christi
Alston.cobourn at tamucc.edu<mailto:Alston.cobourn at tamucc.edu>
361-825-2300<tel:(361)%20825-2300>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=g-ybegHjMclwgD41hYEfOGy4CF58z_BGQAmSM3TLMsc&s=TxwAVAcW8p_dMw7a6VrqiX7HbWO4h4fTRQLYl6EGQz4&e=>



--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Smith College Special Collections will be closed from June through August 2017 as we move to our interim location and Neilson Library<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.smith.edu_libraries_redesign&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=g-ybegHjMclwgD41hYEfOGy4CF58z_BGQAmSM3TLMsc&s=a_iKYBzMTbsUTLbvE0YZKWEDY09BD4wh6vCqghlzbk0&e=> begins renovations. Although we cannot serve researchers onsite during that time, please don't hesitate to be in touch for remote research assistance.

Facebook: https://www.facebook.com/SophiaSmithCollection/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_SophiaSmithCollection_&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=g-ybegHjMclwgD41hYEfOGy4CF58z_BGQAmSM3TLMsc&s=N4XTlPDO18bCv3B52RUa6TSeTe8ntAzxUgjbwS-DiBE&e=>
Instagram: https://www.instagram.com/smithlibraries/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.instagram.com_smithlibraries_&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=g-ybegHjMclwgD41hYEfOGy4CF58z_BGQAmSM3TLMsc&s=ZNf_sTDZN8WykzvSrEAY-b73CGM0kAt-2j4WWUZKaJg&e=>
Twitter: https://twitter.com/archivalagents<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_archivalagents&d=CwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=g-ybegHjMclwgD41hYEfOGy4CF58z_BGQAmSM3TLMsc&s=luf3zGU7l9DfnDliifTday9dmmua9OXIinmZjymriaQ&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/7bb9bdd2/attachment-0001.html>

From christine.dibella at lyrasis.org  Thu Feb 16 08:43:00 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 16 Feb 2017 13:43:00 +0000
Subject: [Archivesspace_Users_Group] JIRA issues cleanup ?
	[was:	Enumerations Findings]
In-Reply-To: <2E477697-0142-4AF3-AD06-159DB1A8E4CF@eservices.virginia.edu>
References: <CAPsSwYrZd+YV5E26Xce5ZNfHm-1pbgyL6zMgOx7CQEzcSZRXJQ@mail.gmail.com>
 <B12EB058-4BD2-496B-B0E7-18E4AC023355@eservices.virginia.edu>
 <f1ded6345ae04863b21138afce1d1341@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB75442@CIO-TNC-D2MBX06.osuad.osu.edu>
 <5ffc8e1bbf4447f6ae49220ad67dad84@ENCTCEXCH008.PA.LCL>
 <EB7C977DC024F8499C24E2B2A11E83A58AB7547C@CIO-TNC-D2MBX06.osuad.osu.edu>
 <CAFfoRK7Y3tPcH-P_8tzRuEjox=mp9y4OE5WmWyAM4apWm5TuFA@mail.gmail.com>
 <3A9B438F-260A-428C-8900-905B10A5B0D3@eservices.virginia.edu>
 <EB7C977DC024F8499C24E2B2A11E83A58AB755D8@CIO-TNC-D2MBX06.osuad.osu.edu>
 <06CF0006-9209-4C73-82CC-92782A88F4BC@eservices.virginia.edu>
 <2E477697-0142-4AF3-AD06-159DB1A8E4CF@eservices.virginia.edu>
Message-ID: <CY1PR08MB1399CC8040E66BFFCBC3EBEAF15A0@CY1PR08MB1399.namprd08.prod.outlook.com>

Hi everyone,

Just to provide a little context for the JIRA issues cleanup specifically, Laney and I are in the process of working with others on improving some processes and workflows related to JIRA. But in the way JIRA has been used for the last couple years, both of the issues Steve points to in his message are resolved, as are any other issues with an ?Accepted? status. ?Accepted? in our past/present usage means code has been delivered and tested that fixes the issue, or that something else has happened that indicates this issue has reached the end of the line. (If what has happened is more complex than just that it got fixed, there is usually a comment trail on the issue that gives an indication.) We have a number of resources for understanding our current use of JIRA on the wiki at https://archivesspace.atlassian.net/wiki/display/ADC/JIRA+Resources. As the process evolves over the coming months with the new crew in place, we?ll update these, but they do reflect how things have worked to now.

We?ve heard feedback across the board that people find our use of JIRA and its relationship to Github confusing, and that it?s difficult for people to determine if an issue has been reported and what?s going on with it once it has been. Improving this experience is very high on our priority list and we very much welcome suggestions. As Steve says, there?s been a changing of the guard and that provides an opportunity for us to reexamine various processes and policies and work with all of you to improve them.

(On the specific issue of what?s going on with being able to import diacritics/special characters, in general, known issues have been fixed over the years. Determining whether there are still issues often does require examination of the specific file being imported and analyzing whether it?s actually something about the encoding in the file or particular data that is presenting a problem. If the encoding and data look OK, then we need to dig deeper, which many on this list are really expert at doing, as we?ve seen!)

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]




From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 5:25 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] JIRA issues cleanup ? [was: Enumerations Findings]


BTW: I know there?s been a recent changing of the guard, so cleanup of JIRA issues may have been neglected, but on this subject:  I believe ar-1421 and ar-647 can both be marked as closed ( and probably several others. Or is this status being tracked somewhere else?  )


https://archivesspace.atlassian.net/browse/AR-1421?jql=text%20~%20%22utf-8%22

https://archivesspace.atlassian.net/browse/AR-647?jql=text%20~%20%22utf-8%22


? Steve.



On Feb 15, 2017, at 4:04 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:

Yes, and the previous cases I?ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn?t being preserved on some other
( xml or json ) internal transform. So that might be something to look for if it?s still happening in a new use case.



On Feb 15, 2017, at 3:54 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:

I?d be interested in the same thing (a sample file).  I?m familiar with the tools being used, and if the data is UTF8, then you shouldn?t see this problem unless the import is munging the data or encoding ? which would be a much different problem.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 3:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


Do you have a sample import file that fails this way ?
Do you know if it still fail on current release ?
( and is bug reported on Jira ? )

? Steve.


On Feb 15, 2017, at 3:25 PM, Lisa Calahan <lcalahan at umn.edu<mailto:lcalahan at umn.edu>> wrote:

I've also received the same UTF8 error when importing legacy accession records that have validdiacritical marks in the title and/or agent name.

Lisa

On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. <reese.2179 at osu.edu<mailto:reese.2179 at osu.edu>> wrote:
I guess my question would be ? is your legacy data UTF8?  For whatever reason, I?ve found that historically, Archives have often used other charactersets when encoding their EAD files (though to be fair, I see this in MARC records as well; confusion between MARC8, ISO8859-1, and codepage 1252).  The simply solution (and this would maintain your characters) would be to convert the character set to UTF8.  Otherwise, even if you held on to these values ? they wouldn?t display in any form that you could read; and in fact, that is what the error message is trying to tell you.  That as a UTF8 value, your data is going to be gibberish, regardless of if you keep it or not.

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 3:12 PM

To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings


I totally agree that we shouldn?t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials.

Suzanne

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Reese, Terry P.
Sent: Wednesday, February 15, 2017 2:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

Why would you want to retain invalid special characters?  My guess is that one of the reasons for this error is that invalid characters would cause problems with indexing for search, as well as impact display and export.  I would think you?d want to use the error as a flag to identify data that needs to be corrected.  Or am I missing something?

--tr

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne
Sent: Wednesday, February 15, 2017 2:52 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I?m not sure quite how to adjust to accept those special characters.

<image002.png>

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
Phone: 717-787-5953<tel:(717)%20787-5953>
http://www.phmc.pa.gov<http://www.phmc.pa.gov/>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 2:36 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Enumerations Findings



We have run into the case that some EAD attribute values are required to be NMTOKENs, thus no embedded spaces or other disallowed characters. We replaced enumerations with embedded spaces with underscores.

This has only come to my attention in the last week or so, so I haven?t made a thorough investigation of which attributes or which enumerations this applies to ? just fixed them as I?ve encountered that error.

So it may be intentional that it is using the non translated value.
( And I wouldn?t be surprised, if for simplicity, it may be over applying that rule in places where it?s not actually required. )


? Steve.


On Feb 15, 2017, at 2:09 PM, Carlos Lemus <carlos.lemus at unlv.edu<mailto:carlos.lemus at unlv.edu>> wrote:

Hello,

At UNLV Special Collections, we've been working on cleaning up our enumeration values because in many cases there were duplicates caused by imports (i.e value: linear_feet vs value: Linear feet vs Linear Feet). We wanted to stick as close as possible to ArchivesSpace standards and decided to make our enumeration values all lowercase seperated by an underscore and then merge any records with incorrect enumerations into that correct value (i.e value: linear Feet into linear_feet). We also have some custom enumerations such as: value: oversized_box, translation: Oversized Box; digital_file; Digital File

After we had that set up correctly, we had some findings and was wondering if anyone has experienced the same things or had a standard we could use.

1. When generating PDFs and EADs the enumeration values that were custom (such as the oversized_box) would come out as machine readable oversized_box instead of using our local en.yml value (located in the local plugin).
     This was something I found in the EAD serializer (https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/ead.rb#L490) and was able to create a temporary solution of generating it , but required altering the enumeration instead of referencing our file. I thought i'd point it out because anyone creating custom enumerations even with a translation in an en.yml  file would not see their change reflected in the EAD export. (I've attached an image reflecting this) Anyone experience this?

2. Another example of this case was in the container "type" attribute. Before something like Oversized Box would be export to EAD as is because that was it's value in the enumeration. After we changed the value correctly to oversized_box, it would export to the EAD container "type" as is and translate to the PDF as well. With some XSLT manipulation I was able to get it to show up as oversized box (shown in attachments). I've looked through https://www.loc.gov/ead/tglib/elements/container.html and cannot find an example of a two+ attribute value.

Should attributes be machine readable (i.e oversized_box), human readable (Oversized Box), or does it even matter? Of course, exporting it as Oversized Box would be easiest to translate a user friendly version to the user.

Excuse me for the lengthy post, I'm trying to be thorough with my explenation, but please let me know if you've come accross something similar or have a finite solution.

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? - Sherlock Holmes
<enumeration_ead.PNG><containers_enum.PNG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--

Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/d1432250/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/d1432250/attachment.jpg>

From christine.dibella at lyrasis.org  Thu Feb 16 09:00:40 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 16 Feb 2017 14:00:40 +0000
Subject: [Archivesspace_Users_Group] Error Running Report
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D381E57@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D381E57@bmcmail2.PABMC.NET>
Message-ID: <CY1PR08MB13994D8AD2C29480903333CDF15A0@CY1PR08MB1399.namprd08.prod.outlook.com>

Dear Jesse,

This is an area the is under very active revision and development right now and I'm afraid what reports are available and working is a bit of a moving target. The Reports subteam of the ArchivesSpace User Advisory Council is preparing a message that explains what is going on, but information about their current work is available on our wiki at https://archivesspace.atlassian.net/wiki/display/AC/ArchivesSpace+Reports.

The March release of ArchivesSpace will remove any reports that are not working and aim to get the highest priority reports from the list at the bottom of https://archivesspace.atlassian.net/wiki/pages/viewpage.action?pageId=98009123 working again. Additional work on reports is being evaluated for the June release.

In case it is helpful for you, I'll mention a couple other workarounds for working with your data. The v1.5 versions provide a way for getting data out in CSV format. You can access this option from the Browse or search results page for any of the primary record types (Accessions, Resources, Digital Objects, Agents, etc.). This will export every field from every record in the result set, but the data can be refined outside ArchivesSpace.

Another option that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy's talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy's starts on page 40. (There are lots of other great talks in this file too!)

I hope this helps a bit. We know that these issues with reports present significant difficulties for people and we're working to resolve them as quickly as we can, but it's a complex process, unfortunately.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse
Sent: Monday, February 13, 2017 9:50 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Error Running Report

I just finished migrating from Archon to AS 1.4.2 and have moved the installation to our production server. Everything seems to be running fine, except for some of the reports. When running the DigitalObjectListReport, for example, the attached error shows up. About 12 of the reports generate a similar error. On the migration server, they ran fine. Any help would be appreciated.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/40aad762/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/40aad762/attachment.jpg>

From smithkr at mit.edu  Thu Feb 16 09:55:48 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Thu, 16 Feb 2017 14:55:48 +0000
Subject: [Archivesspace_Users_Group] XLink value question for DO
 Instance	File Version
In-Reply-To: <F53CDAA0-977D-4C3D-943B-BC151274729D@eservices.virginia.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01047FDA12@OC11expo28.exchange.mit.edu>
 <BD1DE40D-D5C2-4633-A2DC-0918B132521D@eservices.virginia.edu>
 <29F559819ACA9A4FBF208407D4B63ABB01047FDA76@OC11expo28.exchange.mit.edu>
 <F53CDAA0-977D-4C3D-943B-BC151274729D@eservices.virginia.edu>
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01047FF006@OC11expo28.exchange.mit.edu>

Steve, that worked!   Adding in the %20 for spaces in the URL made it valid and so recoginized. This also explains why sometimes the XLink settings were working and other times were not.

Thank you.
Kari


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 5:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version


It?s the spaces in the URL which are causing it to fail converting the string to a URI.


[2] pry(main)> u=URI( 'http://abc/def ghi xxx.pdf' )
URI::InvalidURIError: bad URI(is not URI?): http://abc/def ghi xxx.pdf
from /usr/local/var/rbenv/versions/jruby-1.7.24/lib/ruby/1.9/uri/common.rb:176:in `split'



So the template falls thru to the final case of just displaying the string, instead of the ?link_to? block above:

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/records/_file_versions.html.erb#L12


Try URL encoding the spaces as ?%20? : that should work.


I also tested on 1.4.2. That link above in current release shows the same code in the template.
I don?t know if it checks for valid URL anywhere else in current release.
Perhaps the edit form should take care of checking and encoding when saved.
Will look into this further.


? Steve.


On Feb 15, 2017, at 4:02 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Screenshot attached.  Yes, full URLs.

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, February 15, 2017 4:01 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version


Are they full http:|https: URLs ?
( I know there?s some code that, if there is no scheme in the URLs, assumes they are file: URLs and prepends that scheme. That, and some Windows specific backslash hacks should probably be redone. )

Can you give example of the URLs and maybe a screen shot ?

? Steve.


On Feb 15, 2017, at 3:54 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:

Hi all,
I?m having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help.

My XLink Actuate is OnLoad
XLink Show is embed

The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display to the user.

I feel like this is something I should be able to do but am having trouble even after trying several combinations of the two XLink values.

We are in version 1.4.2  so would be as happy to hear that this is a known version issue. If that?s the case, what would be my ideal values for my ideal behavior in version 1.5.3?

Thanks very much!

Kari R. Smith
Digital Archivist and Program Head for Born-digital Archives
Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts
617.253.5690   smithkr at mit.edu<http://mit.edu/>   http://libraries.mit.edu/archives/  @karirene69

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

<URLnoLink_FileVersion.JPG>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/8442ef65/attachment.html>

From zachary.pelli at shu.edu  Thu Feb 16 11:03:27 2017
From: zachary.pelli at shu.edu (Zachary L Pelli)
Date: Thu, 16 Feb 2017 16:03:27 +0000
Subject: [Archivesspace_Users_Group] Setting up SSL - binding port 443 to
	Apache
Message-ID: <CY4PR01MB221521EF2B231A50237DDAC6E65A0@CY4PR01MB2215.prod.exchangelabs.com>

I am following these directions to set up our AS for SSL:

https://github.com/archivesspace/archivesspace/blob/master/README_HTTPS.md

Now I have run in to an issue. I set up the firewall, configure the Apache httpd.conf, but when I restart httpd, I get an error. The error comes from the "Listen 443" in the ssl.conf file. According to the Apache error log:

[Wed Feb 15 16:45:50.101298 2017] [core:crit] [pid 16935] (22)Invalid argument: AH00069: make_sock: for address [::]:443, apr_socket_opt_set: (IPV6_V6ONLY)
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
[Wed Feb 15 16:45:50.101339 2017] [mpm_prefork:alert] [pid 16935] no listening sockets available, shutting down
[Wed Feb 15 16:45:50.101341 2017] [:emerg] [pid 16935] AH00019: Unable to open logs, exiting

I nmap the server and I see:

80/tcp   open   http           Apache httpd 2.4.6 ((Red Hat Enterprise Linux)
443/tcp  open   ssl/http       Jetty 8.1.5.v20120716

So it seems Apache cannot bind to the port because ArchivesSpace's Jetty sets up shop on the port. Since I have to go through IT to open any new ports, I would much rather stick to 443 than bind Apache to something else. How could I configure Jetty to NOT listen on 443? Any other possible solutions? Thanks in advance.


Zach Pelli
Digital Collections Developer
Walsh Library, Seton Hall University
973.761.2046

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/65e408a0/attachment.html>

From christine.dibella at lyrasis.org  Thu Feb 16 11:47:06 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 16 Feb 2017 16:47:06 +0000
Subject: [Archivesspace_Users_Group] limited time working group for
 reviewing and revising the digital object exports in ArchivesSpace
Message-ID: <CY1PR08MB13991567CD983810761087A5F15A0@CY1PR08MB1399.namprd08.prod.outlook.com>

Hello ArchivesSpace members,
In the coming months, we're going to be putting out calls for participation in some limited time and scope working groups to make recommendations in particular areas. These will supplement the great work being done by our User Advisory Council and Technical Advisory Council, and their associated subteams.
 The first working group is for people interested in reviewing and revising the digital object exports (Dublin Core, MODS, METS) in ArchivesSpace. The charge for the group is to:

*         Identify a set of recommended data elements for each type of digital object export currently supported by ArchivesSpace

*         Prepare data maps that indicate the recommended data elements for each and identify places where the current export does not meet the recommendations
It's possible that, after the initial task is complete, the scope of work could be broadened, including identifying whether there are additional digital object exports that should be supported. The first task, however, is to review and revise the data maps for the existing exports, which will provide us with the specification information we need in order to work with developers on making changes in the application. Once this group has been assembled we'll talk more specifically about timelines, but the hope is that the group's initial work would be completed by the end of April.
If you are interested in participating in this group, or know a colleague who should be included, please email me by March 1. Also, if you have questions or suggestions for other working groups (next on the list is a group to evaluate the MARCXML import and export), please don't hesitate to get in touch.
 Christine
Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/4e1c3f74/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/4e1c3f74/attachment.jpg>

From egadsby at towson.edu  Thu Feb 16 15:39:59 2017
From: egadsby at towson.edu (Gadsby, Eric T.)
Date: Thu, 16 Feb 2017 20:39:59 +0000
Subject: [Archivesspace_Users_Group] Limiting RAM usage by Java and AS
Message-ID: <3AE0CB86-4E32-451D-85A3-185C9460E324@towson.edu>

Dear Friends,

We our AS install is eating up a lot of RAM as Java is known to do. I know other Java based applications I have administered sometimes have ways to limit java ram usage. Is this true for AS?  If so how does one do it. Please pardon if the question asked before. Thanks! 

Sincerely,

Eric T Gadsby
IT Operations Specialist, Cook Library
Towson University
egadsby at towson.edu
410-704-3340


From jvb at louisiana.edu  Thu Feb 16 16:23:36 2017
From: jvb at louisiana.edu (Johna L VonBehrens)
Date: Thu, 16 Feb 2017 15:23:36 -0600 (CST)
Subject: [Archivesspace_Users_Group] Public User Interface PDF Button
In-Reply-To: <mailman.3648.1487251387.29741.archivesspace_users_group@lyralists.lyrasis.org>
References: <mailman.3648.1487251387.29741.archivesspace_users_group@lyralists.lyrasis.org>
Message-ID: <144718616.14015075.1487280216307.JavaMail.zimbra@louisiana.edu>

I am not able to find how to get the PDF button on the collection page in the public user interface.

Any help would be greatly appreciated!
Johna

From j at minorscience.com  Fri Feb 17 13:40:34 2017
From: j at minorscience.com (Jason Loeffler)
Date: Fri, 17 Feb 2017 13:40:34 -0500
Subject: [Archivesspace_Users_Group] query patterns for strings
Message-ID: <CAP4gJsWmkLW9s+PkBWiPRSjvE1uBTewEE1XtQf8+QsnKvhgsng@mail.gmail.com>

This example works taking into account solr/schema.xml
<https://github.com/hudmol/archivesspace/blob/0bdeaabc6b3e8c878590e3d4db0e8c5b99b8c344/solr/schema.xml>
:

search?page=1&?page_size=1&aq={"query":{"field":"title","value":"foo","jsonmodel_type":"field_query"}}'

This example returns "Unrecognized search field: id".

search?page=1&?page_size=1&aq={"query":{"field":"id","value":"anything","jsonmodel_type":"field_query"}}'

Is there an additional parameter required to address fields where
type="string"?

JL

Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
jason at minorscience.com
(347) 405-0826
minorscience (Skype)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170217/27cc891e/attachment.html>

From Alston.Cobourn at tamucc.edu  Fri Feb 17 16:57:38 2017
From: Alston.Cobourn at tamucc.edu (Cobourn, Alston)
Date: Fri, 17 Feb 2017 21:57:38 +0000
Subject: [Archivesspace_Users_Group] EAD import completed but resource,
 subject, agent records not/half created
Message-ID: <DM2PR0601MB1198683B1783304567415B47E05D0@DM2PR0601MB1198.namprd06.prod.outlook.com>

On February 10 I asked for advice on the problem of EAD import completing and creating Resource, Agent, and Subject records but those records then not being findable by browse or search. We subsequently discovered that we were having the same problem with Agent records created through the LCNAF plugin.

And then I discovered that when we link an Agent record to a Resource or Accession record that link is not reflected in the Linked Records section of the Agent record. It is however reflected in the Agents section of the linked Accession or Resource record, and if we update the Agent record, that change is reflected in the linked Accession or Resource record.

It was suggested to me by someone on list that we try restarting our ArchivesSpace instance.  Our IT has now done that and the problems described above persist. Has anyone else experienced any of the above problems?  We are on 1.4.2.  Could this somehow be related to Solr?


Thanks much,

Alston Cobourn

________________________________________________________

Dear all,

Yesterday I tested out EAD import into the AS 1.4.2 test repository of the production instance at the university to which I have recently moved.  I uploaded an EAD XML file that I had generated from the 1.5.2 AS repository at my last job.  The import says it completed successfully and the import log below seems to support that.  All the subjects and agents in the EAD are listed below the log in the New & Modified Records section, and if you click them they do link to newly created Agent and Subject records that say they are linked to no resources.

However, if I browse Agents and Subjects none of the newly created Agents and Subjects are listed.  If I search for the newly created Agents and Subjects they are not findable.  So I have some evidence that says they were created and other evidence that says they weren't.  The resource record I intended to create is also not findable via search or browsing, so it would appear that it was not created, which I don't understand since the background job says completed.

I thought originally that perhaps this was an indexing issue, so I waited overnight but have the same results this morning.  Also, I am able to manually add subjects, agents, and resource records in AS and have them appear via search and browse immediately afterwards.

Does anyone have thoughts as to what could be going on?

==================================================
WLU.Coll.0128_ead.xml
==================================================
1. STARTED: Reading JSON records
1. DONE: Reading JSON records
2. STARTED: Validating records and checking links
2. DONE: Validating records and checking links
3. STARTED: Evaluating record relationships
3. DONE: Evaluating record relationships
4. STARTED: Saving records: cycle 1
Created: /agents/corporate_entities/import_7e59a12f-b7de-4fb1-9527-c2560077d28a
Created: /subjects/import_4430d7be-8431-4758-9d1b-72cb8a16e982
Created: /subjects/import_f9dad788-a3a5-4b90-be77-20b661d9e3b8
Created: /subjects/import_a2c7311f-fd06-42ca-afcb-7c31b98c6442
Created: /agents/corporate_entities/import_c12b78d0-3bf4-4a66-9d13-c67de471fa44
Created: /repositories/import/resources/import_ef64de18-8bf5-4d50-ad06-8ebabda82e52
4. DONE: Saving records: cycle 1
5. STARTED: Cleaning up
5. DONE: Cleaning up





Alston Cobourn
Processing and Digital Assets Archivist
Texas A&M University-Corpus Christi
alston.cobourn at tamucc.edu
361-825-2300

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170217/69843956/attachment.html>

From harnold at rockarch.org  Fri Feb 17 18:02:03 2017
From: harnold at rockarch.org (Arnold, Hillel)
Date: Fri, 17 Feb 2017 23:02:03 +0000
Subject: [Archivesspace_Users_Group] query patterns for strings
In-Reply-To: <CAP4gJsWmkLW9s+PkBWiPRSjvE1uBTewEE1XtQf8+QsnKvhgsng@mail.gmail.com>
References: <CAP4gJsWmkLW9s+PkBWiPRSjvE1uBTewEE1XtQf8+QsnKvhgsng@mail.gmail.com>
Message-ID: <48237FF9-B4BE-49C8-9465-CB9958CCAC7A@rockarch.org>

Hi Jason,
I think you need to use ?identifier? rather than ?id?, like:
search?page=1&?page_size=1&aq={"query":{"field":"identifier","value":"anything","jsonmodel_type":"field_query"}}'

Hillel

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jason Loeffler <j at minorscience.com>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, February 17, 2017 at 1:40 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] query patterns for strings

This example works taking into account solr/schema.xml<https://github.com/hudmol/archivesspace/blob/0bdeaabc6b3e8c878590e3d4db0e8c5b99b8c344/solr/schema.xml>:

search?page=1&?page_size=1&aq={"query":{"field":"title","value":"foo","jsonmodel_type":"field_query"}}'

This example returns "Unrecognized search field: id".

search?page=1&?page_size=1&aq={"query":{"field":"id","value":"anything","jsonmodel_type":"field_query"}}'

Is there an additional parameter required to address fields where type="string"?

JL

Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
jason at minorscience.com<mailto:jason at minorscience.com>
(347) 405-0826
minorscience (Skype)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170217/da385e35/attachment.html>

From j at minorscience.com  Fri Feb 17 18:39:01 2017
From: j at minorscience.com (Jason Loeffler)
Date: Fri, 17 Feb 2017 18:39:01 -0500
Subject: [Archivesspace_Users_Group] query patterns for strings
In-Reply-To: <48237FF9-B4BE-49C8-9465-CB9958CCAC7A@rockarch.org>
References: <CAP4gJsWmkLW9s+PkBWiPRSjvE1uBTewEE1XtQf8+QsnKvhgsng@mail.gmail.com>
 <48237FF9-B4BE-49C8-9465-CB9958CCAC7A@rockarch.org>
Message-ID: <CAP4gJsV6UW7s4DFmoMmibMh3BSNV7xTK98kvPF8XH-nfM0HFoQ@mail.gmail.com>

Thanks, Hillel.

Sure, for Accessions that works.

But I'm targeting 'id'
<https://github.com/archivesspace/archivesspace/blob/master/solr/schema.xml#L49>,
which, in this case, is ambiguous. The request needs a further type
parameter, something like &type[]=archival_object but I can't figure out
the correct pattern based on the autodocs.

On Fri, Feb 17, 2017 at 6:02 PM, Arnold, Hillel <harnold at rockarch.org>
wrote:

> Hi Jason,
>
> I think you need to use ?identifier? rather than ?id?, like:
>
> search?page=1&?page_size=1&aq={"query":{"field":"identifier"
> ,"value":"anything","jsonmodel_type":"field_query"}}'
>
>
>
> Hillel
>
>
>
> *From: *<archivesspace_users_group-bounces at lyralists.lyrasis.org> on
> behalf of Jason Loeffler <j at minorscience.com>
> *Reply-To: *Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Date: *Friday, February 17, 2017 at 1:40 PM
> *To: *Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject: *[Archivesspace_Users_Group] query patterns for strings
>
>
>
> This example works taking into account solr/schema.xml
> <https://github.com/hudmol/archivesspace/blob/0bdeaabc6b3e8c878590e3d4db0e8c5b99b8c344/solr/schema.xml>
> :
>
>
>
> search?page=1&?page_size=1&aq={"query":{"field":"title","
> value":"foo","jsonmodel_type":"field_query"}}'
>
>
>
> This example returns "Unrecognized search field: id".
>
>
>
> search?page=1&?page_size=1&aq={"query":{"field":"id","value"
> :"anything","jsonmodel_type":"field_query"}}'
>
>
>
> Is there an additional parameter required to address fields where
> type="string"?
>
>
>
> JL
>
>
>
> Jason Loeffler
>
> Technology Consultant | The American Academy in Rome
>
> Minor Science | Application Development & Metadata Strategy
>
> Brooklyn, New York
>
> jason at minorscience.com
>
> (347) 405-0826
>
> minorscience (Skype)
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170217/e5571bae/attachment.html>

From sdm7g at eservices.virginia.edu  Sat Feb 18 00:19:39 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Sat, 18 Feb 2017 05:19:39 +0000
Subject: [Archivesspace_Users_Group] EAD import completed but resource,
 subject, agent records not/half created
In-Reply-To: <DM2PR0601MB1198683B1783304567415B47E05D0@DM2PR0601MB1198.namprd06.prod.outlook.com>
References: <DM2PR0601MB1198683B1783304567415B47E05D0@DM2PR0601MB1198.namprd06.prod.outlook.com>
Message-ID: <FEB51F90-3FAC-4712-BCDC-837B8D135C02@eservices.virginia.edu>


I just tested an import on v1.4.2 of an EAD with subjects and agents elements and it all seems to appear for me.

You might check using the backend API to see if the subject and agents are visible there.

Using the curl_as or curl_as_osx scripts the source distribution or github check

   http://backend.host:port/subjects?all_ids=true

and you?ll get an array of subject id numbers. The last numbers should be the last ones created, so with one of those ids, check:

   http://backend.host:port/subjects/id


Alternatively, you can look at the subject table in mysql: "select id,title from subject order by id;?

I?m using subjects as an example because it?s simpler that agents ? there are different kinds of agents so there are more places to look. But you can check agents as well if you know where to look.

If you can find one of your recently created subject, then they were created and it?s likely it is a problem with indexing.


You can also try inspecting the solr web console ? by default port 8090.
Try q -> ?types:subject? in the query form.


If that is the problem, you can try shutting down archivesspace, delete data/indexer_state/* files, and restart archivesspace and see if they appear.

You might also monitor the log file to see if there are any indexer errors.

( This is a lot easier to see if you can run servers separately in development mode. In production, logs from all servers are in a single stream, so if there?s other activity it may be hard to catch. If you can?t do this, it may help to do this when there is little other activity besides the indexing on the servers. )


In another recent thread about broken container indexing in v1.5.x, when the indexer hit an error, it kept attempting to reindex the same records that caused the error, and so nothing after that bad record ever got indexed. So it may be possible that there?s a record causing the indexer to break that is prior to the current imports that seem to be failing.  If you want to post sample files, I can try importing them, but the fact that you?re not seeing results from different imports makes me suspect that if it?s not something fixed by restarting and reindexing, it may be this sort of blockage.



? Steve.





On Feb 17, 2017, at 4:57 PM, Cobourn, Alston <Alston.Cobourn at tamucc.edu<mailto:Alston.Cobourn at tamucc.edu>> wrote:


On February 10 I asked for advice on the problem of EAD import completing and creating Resource, Agent, and Subject records but those records then not being findable by browse or search. We subsequently discovered that we were having the same problem with Agent records created through the LCNAF plugin.

And then I discovered that when we link an Agent record to a Resource or Accession record that link is not reflected in the Linked Records section of the Agent record. It is however reflected in the Agents section of the linked Accession or Resource record, and if we update the Agent record, that change is reflected in the linked Accession or Resource record.

It was suggested to me by someone on list that we try restarting our ArchivesSpace instance.  Our IT has now done that and the problems described above persist. Has anyone else experienced any of the above problems?  We are on 1.4.2.  Could this somehow be related to Solr?


Thanks much,

Alston Cobourn

________________________________________________________

Dear all,

Yesterday I tested out EAD import into the AS 1.4.2 test repository of the production instance at the university to which I have recently moved.  I uploaded an EAD XML file that I had generated from the 1.5.2 AS repository at my last job.  The import says it completed successfully and the import log below seems to support that.  All the subjects and agents in the EAD are listed below the log in the New & Modified Records section, and if you click them they do link to newly created Agent and Subject records that say they are linked to no resources.

However, if I browse Agents and Subjects none of the newly created Agents and Subjects are listed.  If I search for the newly created Agents and Subjects they are not findable.  So I have some evidence that says they were created and other evidence that says they weren't.  The resource record I intended to create is also not findable via search or browsing, so it would appear that it was not created, which I don't understand since the background job says completed.

I thought originally that perhaps this was an indexing issue, so I waited overnight but have the same results this morning.  Also, I am able to manually add subjects, agents, and resource records in AS and have them appear via search and browse immediately afterwards.

Does anyone have thoughts as to what could be going on?

==================================================
WLU.Coll.0128_ead.xml
==================================================
1. STARTED: Reading JSON records
1. DONE: Reading JSON records
2. STARTED: Validating records and checking links
2. DONE: Validating records and checking links
3. STARTED: Evaluating record relationships
3. DONE: Evaluating record relationships
4. STARTED: Saving records: cycle 1
Created: /agents/corporate_entities/import_7e59a12f-b7de-4fb1-9527-c2560077d28a
Created: /subjects/import_4430d7be-8431-4758-9d1b-72cb8a16e982
Created: /subjects/import_f9dad788-a3a5-4b90-be77-20b661d9e3b8
Created: /subjects/import_a2c7311f-fd06-42ca-afcb-7c31b98c6442
Created: /agents/corporate_entities/import_c12b78d0-3bf4-4a66-9d13-c67de471fa44
Created: /repositories/import/resources/import_ef64de18-8bf5-4d50-ad06-8ebabda82e52
4. DONE: Saving records: cycle 1
5. STARTED: Cleaning up
5. DONE: Cleaning up





Alston Cobourn
Processing and Digital Assets Archivist
Texas A&M University-Corpus Christi
alston.cobourn at tamucc.edu<mailto:alston.cobourn at tamucc.edu>
361-825-2300


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170218/c5ae9d46/attachment.html>

From harnold at rockarch.org  Sat Feb 18 11:48:31 2017
From: harnold at rockarch.org (Arnold, Hillel)
Date: Sat, 18 Feb 2017 16:48:31 +0000
Subject: [Archivesspace_Users_Group] query patterns for strings
In-Reply-To: <CAP4gJsV6UW7s4DFmoMmibMh3BSNV7xTK98kvPF8XH-nfM0HFoQ@mail.gmail.com>
References: <CAP4gJsWmkLW9s+PkBWiPRSjvE1uBTewEE1XtQf8+QsnKvhgsng@mail.gmail.com>
 <48237FF9-B4BE-49C8-9465-CB9958CCAC7A@rockarch.org>
 <CAP4gJsV6UW7s4DFmoMmibMh3BSNV7xTK98kvPF8XH-nfM0HFoQ@mail.gmail.com>
Message-ID: <A240FC95-B3E4-45F9-A2FC-845F1E73476B@rockarch.org>

Ah, sorry, read that a little too quickly and didn?t click through on your link the first time around.
Digging backwards, it looks like you might need to add some search definitions here: https://github.com/archivesspace/archivesspace/blob/master/common/search_definitions.rb but I have to admit I?ve never tried it so I might just be making stuff up again!

Hillel

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jason Loeffler <j at minorscience.com>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, February 17, 2017 at 6:39 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] query patterns for strings

Thanks, Hillel.

Sure, for Accessions that works.

But I'm targeting 'id'<https://github.com/archivesspace/archivesspace/blob/master/solr/schema.xml#L49>, which, in this case, is ambiguous. The request needs a further type parameter, something like &type[]=archival_object but I can't figure out the correct pattern based on the autodocs.

On Fri, Feb 17, 2017 at 6:02 PM, Arnold, Hillel <harnold at rockarch.org<mailto:harnold at rockarch.org>> wrote:
Hi Jason,
I think you need to use ?identifier? rather than ?id?, like:
search?page=1&?page_size=1&aq={"query":{"field":"identifier","value":"anything","jsonmodel_type":"field_query"}}'

Hillel

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Jason Loeffler <j at minorscience.com<mailto:j at minorscience.com>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Friday, February 17, 2017 at 1:40 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] query patterns for strings

This example works taking into account solr/schema.xml<https://github.com/hudmol/archivesspace/blob/0bdeaabc6b3e8c878590e3d4db0e8c5b99b8c344/solr/schema.xml>:

search?page=1&?page_size=1&aq={"query":{"field":"title","value":"foo","jsonmodel_type":"field_query"}}'

This example returns "Unrecognized search field: id".

search?page=1&?page_size=1&aq={"query":{"field":"id","value":"anything","jsonmodel_type":"field_query"}}'

Is there an additional parameter required to address fields where type="string"?

JL

Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
jason at minorscience.com<mailto:jason at minorscience.com>
(347) 405-0826<tel:(347)%20405-0826>
minorscience (Skype)


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170218/06cb062d/attachment.html>

From sdm7g at eservices.virginia.edu  Mon Feb 20 16:58:27 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Mon, 20 Feb 2017 21:58:27 +0000
Subject: [Archivesspace_Users_Group] <%= javascript_include_tag
	"application" %>
Message-ID: <F3CB25AD-C4E5-4624-A8EC-D70C1A18242F@eservices.virginia.edu>


I was trying to get some javascript I had working on the frontend app working in the public app as well, and I see that one of my problems was that in the application templates:

 <%= javascript_include_tag "application" %>  

occurs in the head for the frontend but it?s following the footer in the public interface. 

( Thus errors from my header added jQuery code before jQuery loaded. ) 


Is there a reason this is done differently in the two servers ? 
( It makes it kind of awkward to reuse code between the two interfaces. ) 

? Steve. 

From sdm7g at eservices.virginia.edu  Mon Feb 20 18:59:54 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Mon, 20 Feb 2017 23:59:54 +0000
Subject: [Archivesspace_Users_Group] PUI  & ArchivesSpace
Message-ID: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>

What branch or version of ArchivesSpace does the PUI require ? 
I can get it to sort of run, but all of the searches fail. 



From jteitelbaum at pabmc.net  Tue Feb 21 11:05:29 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Tue, 21 Feb 2017 11:05:29 -0500
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed 'Completed' if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/7ebf2a15/attachment.html>

From sdm7g at eservices.virginia.edu  Tue Feb 21 11:15:56 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Tue, 21 Feb 2017 16:15:56 +0000
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
Message-ID: <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/a4f2396b/attachment.html>

From sdm7g at eservices.virginia.edu  Tue Feb 21 11:23:00 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Tue, 21 Feb 2017 16:23:00 +0000
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
Message-ID: <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/d5f72b96/attachment.html>

From speirce at pabmc.net  Tue Feb 21 11:30:52 2017
From: speirce at pabmc.net (Peirce, Sean E.)
Date: Tue, 21 Feb 2017 11:30:52 -0500
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
 <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>

There are no errors of any kind in the archivesspace.out file, and I did see one line ?Running index round?. Do we need to wait until the indexing is complete first?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/68d160f6/attachment.html>

From sdm7g at eservices.virginia.edu  Tue Feb 21 11:53:25 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Tue, 21 Feb 2017 16:53:25 +0000
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
 <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>
Message-ID: <E32E40AF-DC4D-4E90-A885-2E31BDCF530E@eservices.virginia.edu>


I will do a complete reindex for 1.5.2. You will see indexer progress in archivesspace.out, by repository and by resource category. You can browse the completed categories. When you see multiple ?Running index round? lines repeated, it has indexed everything and it just doing a periodic check for anything new.

So although you can check on progress while it?s still indexing, you should probably wait for it to complete before assuming anything is wrong.


On Feb 21, 2017, at 11:31 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

There are no errors of any kind in the archivesspace.out file, and I did see one line ?Running index round?. Do we need to wait until the indexing is complete first?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/2ad0b6c0/attachment.html>

From speirce at pabmc.net  Tue Feb 21 11:57:28 2017
From: speirce at pabmc.net (Peirce, Sean E.)
Date: Tue, 21 Feb 2017 11:57:28 -0500
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <E32E40AF-DC4D-4E90-A885-2E31BDCF530E@eservices.virginia.edu>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
 <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>
 <E32E40AF-DC4D-4E90-A885-2E31BDCF530E@eservices.virginia.edu>
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D445184@bmcmail2.PABMC.NET>

Patience seems to have paid off, data is now present in interface.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:53 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


I will do a complete reindex for 1.5.2. You will see indexer progress in archivesspace.out, by repository and by resource category. You can browse the completed categories. When you see multiple ?Running index round? lines repeated, it has indexed everything and it just doing a periodic check for anything new.

So although you can check on progress while it?s still indexing, you should probably wait for it to complete before assuming anything is wrong.


On Feb 21, 2017, at 11:31 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

There are no errors of any kind in the archivesspace.out file, and I did see one line ?Running index round?. Do we need to wait until the indexing is complete first?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/445bf683/attachment.html>

From sdm7g at eservices.virginia.edu  Tue Feb 21 12:01:01 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Tue, 21 Feb 2017 17:01:01 +0000
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <C6AAE365E91EEC43876ABA64C804C6E4213D445184@bmcmail2.PABMC.NET>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
 <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>
 <E32E40AF-DC4D-4E90-A885-2E31BDCF530E@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D445184@bmcmail2.PABMC.NET>
Message-ID: <FBE776D5-1FAF-4AB9-A9E5-B2ABCA2D7378@eservices.virginia.edu>


Yes: the top_container migration going from 1.4.x to 1.5.x takes quite a while, depending on how much you?ve got in your repos.



On Feb 21, 2017, at 11:57 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

Patience seems to have paid off, data is now present in interface.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:53 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


I will do a complete reindex for 1.5.2. You will see indexer progress in archivesspace.out, by repository and by resource category. You can browse the completed categories. When you see multiple ?Running index round? lines repeated, it has indexed everything and it just doing a periodic check for anything new.

So although you can check on progress while it?s still indexing, you should probably wait for it to complete before assuming anything is wrong.


On Feb 21, 2017, at 11:31 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

There are no errors of any kind in the archivesspace.out file, and I did see one line ?Running index round?. Do we need to wait until the indexing is complete first?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/92899913/attachment.html>

From jteitelbaum at pabmc.net  Tue Feb 21 12:05:14 2017
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Tue, 21 Feb 2017 12:05:14 -0500
Subject: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show
In-Reply-To: <FBE776D5-1FAF-4AB9-A9E5-B2ABCA2D7378@eservices.virginia.edu>
References: <C6AAE365E91EEC43876ABA64C804C6E4213D445152@bmcmail2.PABMC.NET>
 <A79E8090-CE74-4B0B-BAB0-AEF00ECDB4D4@eservices.virginia.edu>
 <903F2522-8C3E-4F36-8F1C-72A346C00A61@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D44516F@bmcmail2.PABMC.NET>
 <E32E40AF-DC4D-4E90-A885-2E31BDCF530E@eservices.virginia.edu>
 <C6AAE365E91EEC43876ABA64C804C6E4213D445184@bmcmail2.PABMC.NET>
 <FBE776D5-1FAF-4AB9-A9E5-B2ABCA2D7378@eservices.virginia.edu>
Message-ID: <C6AAE365E91EEC43876ABA64C804C6E4213D44518C@bmcmail2.PABMC.NET>

The records are there.  BUT? when I?m logged in and click on the ?gear? symbol, clicking on REPORTS, PLUG-INS, and BACKGROUND JOBS, all bring me to the BACKGROUND JOBS page.  I cannot get to REPORTS or PLUG-INS.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 12:01 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Yes: the top_container migration going from 1.4.x to 1.5.x takes quite a while, depending on how much you?ve got in your repos.



On Feb 21, 2017, at 11:57 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

Patience seems to have paid off, data is now present in interface.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:53 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


I will do a complete reindex for 1.5.2. You will see indexer progress in archivesspace.out, by repository and by resource category. You can browse the completed categories. When you see multiple ?Running index round? lines repeated, it has indexed everything and it just doing a periodic check for anything new.

So although you can check on progress while it?s still indexing, you should probably wait for it to complete before assuming anything is wrong.


On Feb 21, 2017, at 11:31 AM, Peirce, Sean E. <speirce at pabmc.net<mailto:speirce at pabmc.net>> wrote:

There are no errors of any kind in the archivesspace.out file, and I did see one line ?Running index round?. Do we need to wait until the indexing is complete first?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, February 21, 2017 11:23 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] 1.5.2 upgrade but no records to show


Sorry: I missed that you already checked background job logs.
Are there indexer error messages are in the main archivesspace.out log ?

If there?s no other activity on the servers, you should see several lines with timestamps and ?Running index round?

? Steve.


On Feb 21, 2017, at 11:16 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


See another thread on this list about indexing error on 1.5.2, and check your logs for errors the batch container migration jobs.




On Feb 21, 2017, at 11:06 AM, Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>> wrote:

We migrated records from ARCHON to AS 1.4.2, then to upgrade to 1.5.2.  I ran the database upgrade script, then started the archivesspace service. Looking at the Background Job log file, there were no errors. Yet, when we sign on, there is nothing to view, no records at all. I can provide the log file, which also showed ?Completed? if you need to see it.


Jesse Teitelbaum | Associate Archivist
Pennsylvania House of Representatives | Archives
469 Forum Building | Harrisburg PA 17120
Phone: 717.783.3866 | Fax: 717.772.1233
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
www.house.state.pa.us/BMC/archives<http://www.house.state.pa.us/BMC/archives>


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/4e0e16de/attachment.html>

From sdm7g at eservices.virginia.edu  Tue Feb 21 12:18:52 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Tue, 21 Feb 2017 17:18:52 +0000
Subject: [Archivesspace_Users_Group] PUI  & ArchivesSpace
In-Reply-To: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>
References: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>
Message-ID: <46AF401D-FFFB-4D41-A991-BF7A299D4C4B@eservices.virginia.edu>


Sorry: I was asking about running public-new. 
It seems to want to use features of the backend /search API that are not supported in 1.5.3 . 
Is there a different branch of archivesspace that matches up with the new PUI ? 

? Steve. 


> On Feb 20, 2017, at 6:59 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
> 
> What branch or version of ArchivesSpace does the PUI require ? 
> I can get it to sort of run, but all of the searches fail. 
> 
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


From bthomas at tsl.texas.gov  Tue Feb 21 12:51:55 2017
From: bthomas at tsl.texas.gov (Brian Thomas)
Date: Tue, 21 Feb 2017 17:51:55 +0000
Subject: [Archivesspace_Users_Group] Usage stats plugin?
Message-ID: <CY4PR1601MB134973883EA60DEE94CE5DA2FA510@CY4PR1601MB1349.namprd16.prod.outlook.com>

I am looking into the possibility of tracking collection usage stats at the box level, rather than at the resource level. Has anyone already made a plug-in that adds the fields to a container necessary to generate this kind of stat? I didn't see one on the plug-ins page.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: bthomas at tsl.texas.gov
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/30121d95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/30121d95/attachment.png>

From tzittlow at lutheranhistory.org  Tue Feb 21 13:50:05 2017
From: tzittlow at lutheranhistory.org (Todd Zittlow)
Date: Tue, 21 Feb 2017 18:50:05 +0000
Subject: [Archivesspace_Users_Group] Early Question.
Message-ID: <D4B3F0C4630ABA468EB3D63FBDC1991E3A68BA15@Wyneken.chinet.local>

Greetings:

We are glad to join to ArchivesSpace community.  We have never used an archival software program so migrating our legacy data over to this software is going to be a major project.  I'm still learning the way AS employs certain terms.  Perhaps one question will begin to clarify matters.  Our archives has historical organized materials based on the materials type.  We have a microfilm collection, a CD collection, an LP collection, manuscripts collections, etc.   I don't think we will be able to migrate all of our accession records.  For the past 30 years we've had a digital accession ledger.  From 1950-1990 our ledger was handwritten.  And prior to 1950 accessions are recorded in a variety of letter, cards, and other loose papers.  I'm using the microfilm collection as a first test case.  My debate has been when I should enter each reel as a separate resource record or whether I should setup the entire Microfilm collection as a resource record which contains the individual "child" items as a part of it.  Or perhaps there are other options that I can't see that would be better.  I'd appreciate any thoughts.  We installed version 1.5.

thanks,

Todd D. Zittlow
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: (314) 505-7923
Fax: (314) 505-7901
tzittlow at lutheranhistory.org
http://www.concordiahistoricalinstitute.org<http://www.concordiahistoricalinstitute.org/>
[CHI SIGNATURE LINE 4 1 SMALL]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/4d57a90d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 37817 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/4d57a90d/attachment.png>

From bthomas at tsl.texas.gov  Tue Feb 21 14:28:21 2017
From: bthomas at tsl.texas.gov (Brian Thomas)
Date: Tue, 21 Feb 2017 19:28:21 +0000
Subject: [Archivesspace_Users_Group] Early Question.
In-Reply-To: <D4B3F0C4630ABA468EB3D63FBDC1991E3A68BA15@Wyneken.chinet.local>
References: <D4B3F0C4630ABA468EB3D63FBDC1991E3A68BA15@Wyneken.chinet.local>
Message-ID: <CY4PR1601MB1349179366954538358BAFD3FA510@CY4PR1601MB1349.namprd16.prod.outlook.com>

Do you have multiple physical repositories? If not, you might consider a format-based repository style. i.e. Repo1=Microfilm Collections &
Repo2=CD Collection, etc. This isn't necessarily the typical set-up, but it might help you differentiate formats as per your current standard, each thing being able to be its own resource if you choose, while avoiding load time issues involved with resources that have a lot of child records.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: bthomas at tsl.texas.gov
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Todd Zittlow
Sent: Tuesday, February 21, 2017 12:50 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Early Question.

Greetings:

We are glad to join to ArchivesSpace community.  We have never used an archival software program so migrating our legacy data over to this software is going to be a major project.  I'm still learning the way AS employs certain terms.  Perhaps one question will begin to clarify matters.  Our archives has historical organized materials based on the materials type.  We have a microfilm collection, a CD collection, an LP collection, manuscripts collections, etc.   I don't think we will be able to migrate all of our accession records.  For the past 30 years we've had a digital accession ledger.  From 1950-1990 our ledger was handwritten.  And prior to 1950 accessions are recorded in a variety of letter, cards, and other loose papers.  I'm using the microfilm collection as a first test case.  My debate has been when I should enter each reel as a separate resource record or whether I should setup the entire Microfilm collection as a resource record which contains the individual "child" items as a part of it.  Or perhaps there are other options that I can't see that would be better.  I'd appreciate any thoughts.  We installed version 1.5.

thanks,

Todd D. Zittlow
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: (314) 505-7923
Fax: (314) 505-7901
tzittlow at lutheranhistory.org<mailto:tzittlow at lutheranhistory.org>
http://www.concordiahistoricalinstitute.org<http://www.concordiahistoricalinstitute.org/>
[CHI SIGNATURE LINE 4 1 SMALL]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/ed408ebd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 5314 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/ed408ebd/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 37817 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/ed408ebd/attachment-0001.png>

From tzittlow at lutheranhistory.org  Tue Feb 21 14:33:23 2017
From: tzittlow at lutheranhistory.org (Todd Zittlow)
Date: Tue, 21 Feb 2017 19:33:23 +0000
Subject: [Archivesspace_Users_Group] Early Question.
In-Reply-To: <CY4PR1601MB1349179366954538358BAFD3FA510@CY4PR1601MB1349.namprd16.prod.outlook.com>
References: <D4B3F0C4630ABA468EB3D63FBDC1991E3A68BA15@Wyneken.chinet.local>
 <CY4PR1601MB1349179366954538358BAFD3FA510@CY4PR1601MB1349.namprd16.prod.outlook.com>
Message-ID: <D4B3F0C4630ABA468EB3D63FBDC1991E3A68BA5E@Wyneken.chinet.local>

Thanks for that.  We have only one physical repository.  We have over 2000 microfilms in the collection.  It sounds like having that many "child" records under one microfilm resource might not be the best option.

Todd

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas
Sent: Tuesday, February 21, 2017 1:28 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Early Question.

Do you have multiple physical repositories? If not, you might consider a format-based repository style. i.e. Repo1=Microfilm Collections &
Repo2=CD Collection, etc. This isn't necessarily the typical set-up, but it might help you differentiate formats as per your current standard, each thing being able to be its own resource if you choose, while avoiding load time issues involved with resources that have a lot of child records.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: bthomas at tsl.texas.gov
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Todd Zittlow
Sent: Tuesday, February 21, 2017 12:50 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Early Question.

Greetings:

We are glad to join to ArchivesSpace community.  We have never used an archival software program so migrating our legacy data over to this software is going to be a major project.  I'm still learning the way AS employs certain terms.  Perhaps one question will begin to clarify matters.  Our archives has historical organized materials based on the materials type.  We have a microfilm collection, a CD collection, an LP collection, manuscripts collections, etc.   I don't think we will be able to migrate all of our accession records.  For the past 30 years we've had a digital accession ledger.  From 1950-1990 our ledger was handwritten.  And prior to 1950 accessions are recorded in a variety of letter, cards, and other loose papers.  I'm using the microfilm collection as a first test case.  My debate has been when I should enter each reel as a separate resource record or whether I should setup the entire Microfilm collection as a resource record which contains the individual "child" items as a part of it.  Or perhaps there are other options that I can't see that would be better.  I'd appreciate any thoughts.  We installed version 1.5.

thanks,

Todd D. Zittlow
Concordia Historical Institute
804 Seminary Place
Saint Louis, MO 63105
Ph: (314) 505-7923
Fax: (314) 505-7901
tzittlow at lutheranhistory.org<mailto:tzittlow at lutheranhistory.org>
http://www.concordiahistoricalinstitute.org<http://www.concordiahistoricalinstitute.org/>
[CHI SIGNATURE LINE 4 1 SMALL]

Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/80aa494b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/80aa494b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 37817 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/80aa494b/attachment-0001.png>

From james at hudmol.com  Tue Feb 21 16:20:29 2017
From: james at hudmol.com (James Bullen)
Date: Wed, 22 Feb 2017 08:20:29 +1100
Subject: [Archivesspace_Users_Group] PUI  & ArchivesSpace
In-Reply-To: <46AF401D-FFFB-4D41-A991-BF7A299D4C4B@eservices.virginia.edu>
References: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>
 <46AF401D-FFFB-4D41-A991-BF7A299D4C4B@eservices.virginia.edu>
Message-ID: <05A23425-B56F-4F62-87B1-CE65C9F963A7@hudmol.com>


Hi Steve,

The development branch for the new public UI is called pui:
https://github.com/archivesspace/archivesspace/tree/pui

To enable the new version, set this environment variable:
export ASPACE_PUBLIC_NEW=true


Cheers,
James


> On Feb 22, 2017, at 4:18 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
> 
> 
> Sorry: I was asking about running public-new. 
> It seems to want to use features of the backend /search API that are not supported in 1.5.3 . 
> Is there a different branch of archivesspace that matches up with the new PUI ? 
> 
> ? Steve. 
> 
> 
>> On Feb 20, 2017, at 6:59 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
>> 
>> What branch or version of ArchivesSpace does the PUI require ? 
>> I can get it to sort of run, but all of the searches fail. 
>> 
>> 
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:58ac7690219363724355696!


From crluers at wm.edu  Tue Feb 21 17:00:34 2017
From: crluers at wm.edu (Luers, Christina)
Date: Tue, 21 Feb 2017 22:00:34 +0000
Subject: [Archivesspace_Users_Group] Basics of Archives and Digital Objects
	Training
Message-ID: <c1536bdbd96e4a3bbc29ecee5c5954b3@EXMBX03.campus.wm.edu>

Archives Space members,

We are happy to announce that we are able to host Archives Space training at the College of William and Mary in Williamsburg, VA.  Training will take place over a three day period from March 6 (Monday) to March 8 (Wednesday).  The first two days will cover the Basics and will focus on the staff entry of accessions and resources along with various aspects of the staff interface.  The third day is a Digital Objects workshop focused solely on creating and managing digital objects within the functions of Archives Space.  The training will occur in Swem Library's Ford Classroom.  All three days will start around 9am and end close to 5pm with breaks worked into the day throughout and also for lunch.

If you would like to attend, please respond to crluers at wm.edu with names and contact information for each attendee.  Please also indicate if you can bring your own laptop or if you will need for us to provide one to you for your training.

There is no charge for these workshops, and we still have plenty of room.  Please respond by 27 February 2017.


Best,

Christina Luers
crluers at wm.edu


Christina R. Luers
Archives Collections Specialist
Special Collections Research Center
Earl Gregg Swem Library College of William and Mary
P.O. Box 8794
Williamsburg, VA 23187-8794

crluers at wm.edu<mailto:crluers at wm.edu>
757-221-3096



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170221/404e7ee9/attachment.html>

From james at hudmol.com  Tue Feb 21 23:45:02 2017
From: james at hudmol.com (James Bullen)
Date: Wed, 22 Feb 2017 15:45:02 +1100
Subject: [Archivesspace_Users_Group] PUI  & ArchivesSpace
In-Reply-To: <05A23425-B56F-4F62-87B1-CE65C9F963A7@hudmol.com>
References: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>
 <46AF401D-FFFB-4D41-A991-BF7A299D4C4B@eservices.virginia.edu>
 <05A23425-B56F-4F62-87B1-CE65C9F963A7@hudmol.com>
Message-ID: <A8DE01CC-9BC4-4C76-9659-BC7682F934F0@hudmol.com>


Hi again Steve!

Actually, we just did a big merge to pull together a number of development strands for the March release. So now the latest pui code will be in:
https://github.com/archivesspace/archivesspace/tree/march-release


Cheers,
James


> On Feb 22, 2017, at 8:20 AM, James Bullen <james at hudmol.com> wrote:
> 
> 
> Hi Steve,
> 
> The development branch for the new public UI is called pui:
> https://github.com/archivesspace/archivesspace/tree/pui <https://github.com/archivesspace/archivesspace/tree/pui>
> 
> To enable the new version, set this environment variable:
> export ASPACE_PUBLIC_NEW=true
> 
> 
> Cheers,
> James
> 
> 
>> On Feb 22, 2017, at 4:18 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
>> 
>> 
>> Sorry: I was asking about running public-new. 
>> It seems to want to use features of the backend /search API that are not supported in 1.5.3 . 
>> Is there a different branch of archivesspace that matches up with the new PUI ? 
>> 
>> ? Steve. 
>> 
>> 
>>> On Feb 20, 2017, at 6:59 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
>>> 
>>> What branch or version of ArchivesSpace does the PUI require ? 
>>> I can get it to sort of run, but all of the searches fail. 
>>> 
>>> 
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>> 
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>> 
>> 
>> 
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:58acaf3551392126911598!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170222/2416fe1c/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 22 11:33:51 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 22 Feb 2017 16:33:51 +0000
Subject: [Archivesspace_Users_Group] PUI  & ArchivesSpace
In-Reply-To: <A8DE01CC-9BC4-4C76-9659-BC7682F934F0@hudmol.com>
References: <5D502C76-6045-4276-9466-F04FCBEEB8EF@eservices.virginia.edu>
 <46AF401D-FFFB-4D41-A991-BF7A299D4C4B@eservices.virginia.edu>
 <05A23425-B56F-4F62-87B1-CE65C9F963A7@hudmol.com>
 <A8DE01CC-9BC4-4C76-9659-BC7682F934F0@hudmol.com>
Message-ID: <FCF26DA4-E034-4040-AB4F-190618324E1A@eservices.virginia.edu>


Thanks: great news. Will try to get it running on our test server soon. ? Steve.

On Feb 21, 2017, at 11:41 PM, James Bullen <james at hudmol.com<mailto:james at hudmol.com>> wrote:


Hi again Steve!

Actually, we just did a big merge to pull together a number of development strands for the March release. So now the latest pui code will be in:
https://github.com/archivesspace/archivesspace/tree/march-release


Cheers,
James


On Feb 22, 2017, at 8:20 AM, James Bullen <james at hudmol.com<mailto:james at hudmol.com>> wrote:


Hi Steve,

The development branch for the new public UI is called pui:
https://github.com/archivesspace/archivesspace/tree/pui

To enable the new version, set this environment variable:
export ASPACE_PUBLIC_NEW=true


Cheers,
James


On Feb 22, 2017, at 4:18 AM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:


Sorry: I was asking about running public-new.
It seems to want to use features of the backend /search API that are not supported in 1.5.3 .
Is there a different branch of archivesspace that matches up with the new PUI ?

? Steve.


On Feb 20, 2017, at 6:59 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu<mailto:sdm7g at eservices.virginia.edu>> wrote:

What branch or version of ArchivesSpace does the PUI require ?
I can get it to sort of run, but all of the searches fail.


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group




_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


!DSPAM:58acaf3551392126911598!

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170222/dfe2f2fe/attachment.html>

From sdm7g at eservices.virginia.edu  Wed Feb 22 11:56:26 2017
From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Wed, 22 Feb 2017 16:56:26 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace v1.5.3 released
In-Reply-To: <SN1PR08MB1406CB139F3FFA9FADB6FE16F15B0@SN1PR08MB1406.namprd08.prod.outlook.com>
References: <SN1PR08MB1406CB139F3FFA9FADB6FE16F15B0@SN1PR08MB1406.namprd08.prod.outlook.com>
Message-ID: <E6E8D789-D757-4A68-B148-ABA28552D999@eservices.virginia.edu>


VERY happy to see the slow EAD import problem in 1.5.1 has been fixed somewhere along the way to 1.5.3.
It managed our largest 18MB finding aid with no problem.

? Steve.



On Feb 15, 2017, at 12:19 PM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote:

The ArchivesSpace team is very pleased to release version 1.5.3!

You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3.

This minor release has some bug fixes, including a fix for the issue with resource components being exported in EAD in a different order from how they appear in the staff interface (https://archivesspace.atlassian.net/browse/AR-1620), as well as improvements to overall performance. It features work from our development partner, Hudson Molonglo (HM), as well as code contributions from community members Mark Cooper, Steve Majewski, Chris Fitzpatrick, Jason Loeffler, and Michael Bond. Thanks to all who contributed, participated in testing and provided the feedback that led to these improvements!

?         Please see the release page<https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3> for a listing of all the new features and bug fixes included in this release.

?         Please see the technical documentation<http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/> for information on how to upgrade your ArchivesSpace installations.

Big thanks as always to Mark Cooper, Blake Carver, and the other staff of LYRASIS? Digital Technology Services for their testing and technical support. We?re also pleased to celebrate the first regular release managed by ArchivesSpace?s new Tech Lead, Laney McGlohon.

Please let us know if you have questions or encounter problems executing the upgrade. The next major release of ArchivesSpace, which will include a beta of the new public interface, is expected to be available near the end of March.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

<image002.jpg>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170222/57c50e34/attachment.html>

From carlos.lemus at unlv.edu  Wed Feb 22 13:36:58 2017
From: carlos.lemus at unlv.edu (Carlos Lemus)
Date: Wed, 22 Feb 2017 10:36:58 -0800
Subject: [Archivesspace_Users_Group] Fwd: Enumerations Findings
In-Reply-To: <CAPsSwYrWvT3nU7WyVQihzNp0rQzzzExeBE66CRF0-0RfCKgMaw@mail.gmail.com>
References: <CAPsSwYrWvT3nU7WyVQihzNp0rQzzzExeBE66CRF0-0RfCKgMaw@mail.gmail.com>
Message-ID: <CAPsSwYpq-6cEu=vWT+aSERGZa5dnX6ATjuLPL2XOL1ggwQ-Z8w@mail.gmail.com>

Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

*How often have I said to you that when you have eliminated the impossible,
whatever remains, however improbable, must be the truth? - Sherlock Holmes*

---------- Forwarded message ----------
From: Carlos Lemus <carlos.lemus at unlv.edu>
Date: Wed, Feb 22, 2017 at 10:34 AM
Subject: Enumerations Findings
To: archivesspace at googlegroups.com
Cc: Cynthia Shein <cyndi.shein at unlv.edu>, Carol Ou <carol.ou at unlv.edu>


Hello,

Thank you guys for your interest in this topic. It seems we can all agree
there is some confusion on the creation of controlled values that occur
when there is an import whether it is marc or ead. I've attached a simple
EAD example to import (may not be complete, but does contain some valid
examples). This EAD example was exported from our testing area for
ArchivesSpace and I've round trip it as a new record. While I don't think
we've had any character/UTF8 encoding samples, I wanted to point out some
simpler examples (with incorrect enumerations).

Under the <physdec> -> <extent> -> you will see 1 Linear  Feet. Though it
is correct in the EAD, on import, it will create a new Linear Feet value
instead of using the already existing controlled value of linear_feet.

Similarly, for containers under <container label="Mixed Materials"> it will
create a new enumeration as Mixed Materials instead of mixed_materials.

Evidently, if this happens for many records you'll see many enumeration
values that are not correct under your values when you create a record.  We
are still under 1.4.2 and cannot speak for the new version.

Thank you,
Carlos Lemus
Application Programmer, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas

*How often have I said to you that when you have eliminated the impossible,
whatever remains, however improbable, must be the truth? - Sherlock Holmes*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170222/4aa9e6bd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EAD-TEST-002_ead.xml
Type: text/xml
Size: 18638 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170222/4aa9e6bd/attachment.xml>

From jgd1 at williams.edu  Thu Feb 23 15:58:21 2017
From: jgd1 at williams.edu (Drmacich, Jessika)
Date: Thu, 23 Feb 2017 15:58:21 -0500
Subject: [Archivesspace_Users_Group] MARCXML export
Message-ID: <CAJ3o66zzQEv601pS7G7mFsQCi8skwMcnya68jPM2tONHyQMMRg@mail.gmail.com>

We have noticed that some fields do not export into MARCXML, including
<bioghist>/561 and <prefercite>/524. Has anyone else experienced this
problem, and is there a way to adjust which fields are exported?

Thank you!

Jessika Drmacich
Records Manager & Digital Resources Archivist
Williams College Libraries
Special Collections
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170223/1df9b8e8/attachment.html>

From christine.dibella at lyrasis.org  Mon Feb 27 12:52:21 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Mon, 27 Feb 2017 17:52:21 +0000
Subject: [Archivesspace_Users_Group] FW: limited time working group for
 reviewing and revising the digital object exports in ArchivesSpace
Message-ID: <SN1PR08MB1406FF713FFC9A7EE2C366D8F1570@SN1PR08MB1406.namprd08.prod.outlook.com>

Thanks to those who have responded to this call so far, and those who have suggested other groups! If you'd like to volunteer for the digital object exports group, please let me know by Wednesday, March 1. I'll be in touch with all the volunteers soon afterwards to assemble the group.

Christine

From: Christine Di Bella
Sent: Thursday, February 16, 2017 11:45 AM
To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org>; 'Archivesspace Member Reps' <archivesspace_member_reps at lyralists.lyrasis.org>; 'archivesspace_tac_uac at lyralists.lyrasis.org' <archivesspace_tac_uac at lyralists.lyrasis.org>
Subject: limited time working group for reviewing and revising the digital object exports in ArchivesSpace

Hello ArchivesSpace members,
In the coming months, we're going to be putting out calls for participation in some limited time and scope working groups to make recommendations in particular areas. These will supplement the great work being done by our User Advisory Council and Technical Advisory Council, and their associated subteams.
 The first working group is for people interested in reviewing and revising the digital object exports (Dublin Core, MODS, METS) in ArchivesSpace. The charge for the group is to:

*         Identify a set of recommended data elements for each type of digital object export currently supported by ArchivesSpace

*         Prepare data maps that indicate the recommended data elements for each and identify places where the current export does not meet the recommendations
It's possible that, after the initial task is complete, the scope of work could be broadened, including identifying whether there are additional digital object exports that should be supported. The first task, however, is to review and revise the data maps for the existing exports, which will provide us with the specification information we need in order to work with developers on making changes in the application. Once this group has been assembled we'll talk more specifically about timelines, but the hope is that the group's initial work would be completed by the end of April.
If you are interested in participating in this group, or know a colleague who should be included, please email me by March 1. Also, if you have questions or suggestions for other working groups (next on the list is a group to evaluate the MARCXML import and export), please don't hesitate to get in touch.
 Christine
Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170227/ef9ca107/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170227/ef9ca107/attachment-0001.jpg>

From ksmith115 at po-box.esu.edu  Tue Feb 28 10:34:10 2017
From: ksmith115 at po-box.esu.edu (Kelly J Smith)
Date: Tue, 28 Feb 2017 15:34:10 +0000
Subject: [Archivesspace_Users_Group] bar coding and migration questions
Message-ID: <234F6C9EA172C946BD845144C241DDD2CB482787@MSXMB1.ADMIN.ESU.EDU>

Hello,

I have two questions regarding using ArchivesSpace to manage an art collection.
Is it possible to use item-level bar coding with ArchivesSpace?
Can an Access database be imported to ArchivesSpace?

Thanks.

Kelly Smith

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/059bfb65/attachment.html>

From mkottman at ku.edu  Tue Feb 28 11:22:04 2017
From: mkottman at ku.edu (Kottman, Miloche)
Date: Tue, 28 Feb 2017 16:22:04 +0000
Subject: [Archivesspace_Users_Group] bar coding and migration questions
In-Reply-To: <234F6C9EA172C946BD845144C241DDD2CB482787@MSXMB1.ADMIN.ESU.EDU>
References: <234F6C9EA172C946BD845144C241DDD2CB482787@MSXMB1.ADMIN.ESU.EDU>
Message-ID: <b3b545453a96450c8b2f157e454066fd@ex13-ell-cr-15.home.ku.edu>

Kelly,

If the item is the top container, then yes, you can have a barcode.  For example, if you have an item in a folder and the folder is in a box and you want all that information in the record, the top container is the box - so the box would have a barcode but not the folder or  item.  If you have an item and it's not in a folder or box (or no one needs to know if it's in a folder or a box), then the item is the top container and you would barcode it.
I suppose you could create a series/subseries  that's box 1, (or box 1, folder 1) and add the items as children....

As for the Access database import question, the answer is sorta.  You would need to export the data you want out of Access as an Excel spreadsheet.  If your data is spread across multiple tables, you'll need to create a Make Table query that pulls the data you want and saves it into a separated table.  You can then export the resulting table to Excel, rename column headers and the re-order the columns to match the ArchivesSpace mapping tables and import.  Easier said than done but it is possible.

--Miloche

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kelly J Smith
Sent: Tuesday, February 28, 2017 9:34 AM
To: 'archivesspace_users_group at lyralists.lyrasis.org' <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] bar coding and migration questions

Hello,

I have two questions regarding using ArchivesSpace to manage an art collection.
Is it possible to use item-level bar coding with ArchivesSpace?
Can an Access database be imported to ArchivesSpace?

Thanks.

Kelly Smith

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/599415e3/attachment.html>

From alexanderduryee at nypl.org  Tue Feb 28 12:27:23 2017
From: alexanderduryee at nypl.org (Alexander Duryee)
Date: Tue, 28 Feb 2017 12:27:23 -0500
Subject: [Archivesspace_Users_Group] Intermittent Outages
Message-ID: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>

Our production instance of ASpace has been suffering from intermittent
outages for the past few weeks.  Roughly once or twice a day, the
application will go down for 1-5 minutes, then bring itself back up.
Perplexingly, this doesn't seem to impact the backend - for example, the
application went down during a reindex, but the reindex continued (and was
logged) during the outage.  However, API requests are dropped and the
frontend is inaccessible during the outage.

We haven't identified a cause for the outages (e.g. heavy traffic, lots of
database calls), as there's no consistent pattern.  There's nothing in
archivesspace.out to indicate any troubles.

Has anyone else experienced similar issues?  Is there another log that we
could refer to (e.g. ASpace's Apache instance) to diagnose the outages?

Thanks!
--Alex

-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/6ac2e677/attachment.html>

From clobdel1 at swarthmore.edu  Tue Feb 28 12:47:41 2017
From: clobdel1 at swarthmore.edu (Chelsea Lobdell)
Date: Tue, 28 Feb 2017 12:47:41 -0500
Subject: [Archivesspace_Users_Group] Intermittent Outages
In-Reply-To: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
References: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
Message-ID: <CANoeXEanVS18Ftt6g50LizxTYVrOHvoKCJOouNnzasGi10jF6w@mail.gmail.com>

Hi Alex,

Not sure if this is going to be helpful or not but we were seeing a lot of
CPU load warnings on our dev server that would bring the frontend of the
application to a grinding halt until it was restarted. I was unable to see
anything in the logs or any sort of malicious traffic so I put a few stop
gaps in place. First, I adjusted IP Table and Firewall rules to lock down
the application to only campus IP ranges. The application is only used by
staff currently and they know if they are coming from off campus they need
to use EZProxy or VPN for access. Secondly, I set a nightly restart cron
from the root user's crontab:
# restart archivesspace every night at 2am
00 02 * * * /etc/init.d/archivesspace stop
05 02 * * * /etc/init.d/archivesspace start

We haven't experience CPU load warnings since I put these stop gaps in
place. So I'm still uncertain of what was causing the issue but maybe these
stop gaps can help you too.

- Chelsea

*---------------*
*Chelsea Lobdell*
*Library Web Developer/ Swarthmore College*
*clobdel1 at swarthmore.edu <clobdel1 at swarthmore.edu> / (610)690-6818*

On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee <alexanderduryee at nypl.org
> wrote:

> Our production instance of ASpace has been suffering from intermittent
> outages for the past few weeks.  Roughly once or twice a day, the
> application will go down for 1-5 minutes, then bring itself back up.
> Perplexingly, this doesn't seem to impact the backend - for example, the
> application went down during a reindex, but the reindex continued (and was
> logged) during the outage.  However, API requests are dropped and the
> frontend is inaccessible during the outage.
>
> We haven't identified a cause for the outages (e.g. heavy traffic, lots of
> database calls), as there's no consistent pattern.  There's nothing in
> archivesspace.out to indicate any troubles.
>
> Has anyone else experienced similar issues?  Is there another log that we
> could refer to (e.g. ASpace's Apache instance) to diagnose the outages?
>
> Thanks!
> --Alex
>
> --
> Alexander Duryee
> Metadata Archivist
> New York Public Library
> (917)-229-9590 <(917)%20229-9590>
> alexanderduryee at nypl.org
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/0ab8487b/attachment.html>

From alexanderduryee at nypl.org  Tue Feb 28 13:04:56 2017
From: alexanderduryee at nypl.org (Alexander Duryee)
Date: Tue, 28 Feb 2017 13:04:56 -0500
Subject: [Archivesspace_Users_Group] Intermittent Outages
In-Reply-To: <CANoeXEanVS18Ftt6g50LizxTYVrOHvoKCJOouNnzasGi10jF6w@mail.gmail.com>
References: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
 <CANoeXEanVS18Ftt6g50LizxTYVrOHvoKCJOouNnzasGi10jF6w@mail.gmail.com>
Message-ID: <CAK5BadDuc7bugYOe8S+t3VnhU_qkEswD92FoBn4XT0wYAeFcNQ@mail.gmail.com>

Chelsea,

Thanks for your response!  We aren't seeing any resource usage spikes
during/before outages, and the disk isn't filling up, so that isn't the
issue on our end.  We've already limited ASpace to our internal network, so
it's not a question of extreme traffic.

Thanks,
--Alex

On Tue, Feb 28, 2017 at 12:47 PM, Chelsea Lobdell <clobdel1 at swarthmore.edu>
wrote:

> Hi Alex,
>
> Not sure if this is going to be helpful or not but we were seeing a lot of
> CPU load warnings on our dev server that would bring the frontend of the
> application to a grinding halt until it was restarted. I was unable to see
> anything in the logs or any sort of malicious traffic so I put a few stop
> gaps in place. First, I adjusted IP Table and Firewall rules to lock down
> the application to only campus IP ranges. The application is only used by
> staff currently and they know if they are coming from off campus they need
> to use EZProxy or VPN for access. Secondly, I set a nightly restart cron
> from the root user's crontab:
> # restart archivesspace every night at 2am
> 00 02 * * * /etc/init.d/archivesspace stop
> 05 02 * * * /etc/init.d/archivesspace start
>
> We haven't experience CPU load warnings since I put these stop gaps in
> place. So I'm still uncertain of what was causing the issue but maybe these
> stop gaps can help you too.
>
> - Chelsea
>
> *---------------*
> *Chelsea Lobdell*
> *Library Web Developer/ Swarthmore College*
> *clobdel1 at swarthmore.edu <clobdel1 at swarthmore.edu> / (610)690-6818
> <(610)%20690-6818>*
>
> On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee <
> alexanderduryee at nypl.org> wrote:
>
>> Our production instance of ASpace has been suffering from intermittent
>> outages for the past few weeks.  Roughly once or twice a day, the
>> application will go down for 1-5 minutes, then bring itself back up.
>> Perplexingly, this doesn't seem to impact the backend - for example, the
>> application went down during a reindex, but the reindex continued (and was
>> logged) during the outage.  However, API requests are dropped and the
>> frontend is inaccessible during the outage.
>>
>> We haven't identified a cause for the outages (e.g. heavy traffic, lots
>> of database calls), as there's no consistent pattern.  There's nothing in
>> archivesspace.out to indicate any troubles.
>>
>> Has anyone else experienced similar issues?  Is there another log that we
>> could refer to (e.g. ASpace's Apache instance) to diagnose the outages?
>>
>> Thanks!
>> --Alex
>>
>> --
>> Alexander Duryee
>> Metadata Archivist
>> New York Public Library
>> (917)-229-9590 <(917)%20229-9590>
>> alexanderduryee at nypl.org
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/55a9e689/attachment.html>

From trthorn2 at ncsu.edu  Tue Feb 28 13:13:50 2017
From: trthorn2 at ncsu.edu (Trevor Thornton)
Date: Tue, 28 Feb 2017 13:13:50 -0500
Subject: [Archivesspace_Users_Group] Intermittent Outages
In-Reply-To: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
References: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
Message-ID: <CA+SdyS3+qbdn3+N-CtNk=KR=+Hgz8R9ySC2-pmk5BdyTFGUcog@mail.gmail.com>

I have some tasks that make multiple API calls and recently I've noticed
that the session will sometimes get dropped (API returns 412 response with
a message saying that the token is invalid) after only a few minutes
(should remain valid for 60 minutes). I think it started happening when we
upgraded from 1.4.x to 1.5.1, and it doesn't happen all the time, but I
don't know why it happens when it does.

We've also had cases where AS becomes unresponsive. When this has happened
I would usually just restart it, so I don't know if it would have come back
online if I waited long enough.

On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee <alexanderduryee at nypl.org
> wrote:

> Our production instance of ASpace has been suffering from intermittent
> outages for the past few weeks.  Roughly once or twice a day, the
> application will go down for 1-5 minutes, then bring itself back up.
> Perplexingly, this doesn't seem to impact the backend - for example, the
> application went down during a reindex, but the reindex continued (and was
> logged) during the outage.  However, API requests are dropped and the
> frontend is inaccessible during the outage.
>
> We haven't identified a cause for the outages (e.g. heavy traffic, lots of
> database calls), as there's no consistent pattern.  There's nothing in
> archivesspace.out to indicate any troubles.
>
> Has anyone else experienced similar issues?  Is there another log that we
> could refer to (e.g. ASpace's Apache instance) to diagnose the outages?
>
> Thanks!
> --Alex
>
> --
> Alexander Duryee
> Metadata Archivist
> New York Public Library
> (917)-229-9590 <(917)%20229-9590>
> alexanderduryee at nypl.org
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/da6118b5/attachment.html>

From carrie.daniels at louisville.edu  Tue Feb 28 17:11:27 2017
From: carrie.daniels at louisville.edu (carrie.daniels at louisville.edu)
Date: Tue, 28 Feb 2017 22:11:27 +0000
Subject: [Archivesspace_Users_Group] Intermittent Outages
In-Reply-To: <CA+SdyS3+qbdn3+N-CtNk=KR=+Hgz8R9ySC2-pmk5BdyTFGUcog@mail.gmail.com>
References: <CAK5BadDynkTPVP3emTVT87E5nu9t5CB3h+jv_4=eyjRQpam80A@mail.gmail.com>
 <CA+SdyS3+qbdn3+N-CtNk=KR=+Hgz8R9ySC2-pmk5BdyTFGUcog@mail.gmail.com>
Message-ID: <9A1D5C806D42B64E857CE93DFE714EF1010C2F3317@exmbx04>

We?ve been experiencing something similar, and yet different? We randomly get proxy errors when working in the staff interface. ASpace seems to restart itself after a while. This happens when we are making edits to Accession records. We are running 1.4.2.

Carrie

Carrie Daniels
University Archivist and Director,
Archives and Special Collections
University of Louisville


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton
Sent: Tuesday, February 28, 2017 1:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Intermittent Outages

I have some tasks that make multiple API calls and recently I've noticed that the session will sometimes get dropped (API returns 412 response with a message saying that the token is invalid) after only a few minutes (should remain valid for 60 minutes). I think it started happening when we upgraded from 1.4.x to 1.5.1, and it doesn't happen all the time, but I don't know why it happens when it does.

We've also had cases where AS becomes unresponsive. When this has happened I would usually just restart it, so I don't know if it would have come back online if I waited long enough.

On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee <alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>> wrote:
Our production instance of ASpace has been suffering from intermittent outages for the past few weeks.  Roughly once or twice a day, the application will go down for 1-5 minutes, then bring itself back up.  Perplexingly, this doesn't seem to impact the backend - for example, the application went down during a reindex, but the reindex continued (and was logged) during the outage.  However, API requests are dropped and the frontend is inaccessible during the outage.
We haven't identified a cause for the outages (e.g. heavy traffic, lots of database calls), as there's no consistent pattern.  There's nothing in archivesspace.out to indicate any troubles.
Has anyone else experienced similar issues?  Is there another log that we could refer to (e.g. ASpace's Apache instance) to diagnose the outages?

Thanks!
--Alex

--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590<tel:(917)%20229-9590>
alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMFaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=5Q0_NDfXIo1GAZnkNLoezH8GMwO1xdN0wOFI5K943YY&m=kGT602CWzyOrwnHRaTbTZlx8mypGi3RnMGlORqnEbl0&s=ntesVvh31kp4I80k4af8yJYpCXDDNq6eQ_-xQaGzLY4&e=>



--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/a4942b64/attachment.html>