[Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD <dimensions> and <physfacet>)?

Tue Mar 8 13:54:18 EST 2016

Hi all,

We here at the Bentley submitted that PR a few months ago to fix this
physdesc mapping issue. As far as I can tell, there is no requirement to
have an @altrender="part" attribute; rather, the PR was meant to make
ArchivesSpace ingest physdescs in the same way that it exports them. There
was some discussion about that on the PR here:
https://github.com/archivesspace/archivesspace/pull/312

Basically, the ArchivesSpace EAD exporter exports an extent record's
"portion" value as an altrender attribute of "whole" or "part," so the PR
that we submitted checks for an altrender attribute and, if it finds one
AND the altrender value is "part," the imported extent will have a portion
of "part." Otherwise, in cases where there is no altrender attribute or the
altrender attribute is some value other than "part," the extent record's
portion is set to "whole." See here:
https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252

I just tested importing an EAD with several physdesc variations (some with
altrenders, some without; some with multiple extents, a physfacet and a
dimensions element, some with only a single extent or a single physfacet,
etc.) and it imported as expected (physdescs with an extent + other
elements create only an extent record and no duplicate notes; physdescs
with only non-extent elements create physical facet, physical dimensions,
or physical description notes, and so on). The imported resource is here:
http://test.archivesspace.org/resources/54

As far as I can tell, this issue has been fixed but it just has not made it
into an official release (the PR was accepted last November; v. 1.4.2 came
out in October).

I uploaded the EAD that I just tested to the JIRA issue as
physdesc_variations_test.xml.

On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. <kate_bowers at harvard.edu>
wrote:

> I don’t understand the reasoning behind this at all.  Why would a
> <physdesc> that has <dimensions> or <physfacet>  only ever be a “part”?  Is
> there any documentation of the EAD ingest where this is recorded?
>
>
>
> Thanks!
>
>
> Kate
>
>
>
>
>
>
>
> *Kate Bowers*
>
> Collections Services Archivist for Metadata, Systems, and Standards
>
> Harvard University Archives
>
> kate_bowers at harvard.edu <megan_sniffin-marinoff at harvard.edu>
>
> 617.496.2713
>
> voice: (617) 384-7787
>
> fax: (617) 495-8011
>
> web: http://nrs.harvard.edu/urn-3:hul.eresource:archives
>
> Twitter: @k8_bowers
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Chris
> Fitzpatrick
> *Sent:* Tuesday, March 08, 2016 11:50 AM
>
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Any progress on AR1134
> (ingesting EAD <dimensions> and <physfacet>)?
>
>
>
>
>
>
>
> Hi,
>
>
>
> We did our March sprint planning
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1134&d=CwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=ZiA4lKtFjjvXBp_jnGl60EM_epYBy-o_l1XqJtuMclc&s=WA1pOD-hlNR3C4LiqJXWMQMKvaWY7uuD6sewvznDQqw&e=>
> yesterday afternoon and this feature request was not included in the
> sprint.
>
>
>
> However, looking through this ticket, it looks like a pull request was
> already submitted and accepted that adds this feature. The key is that the
> physdesc has to have an @altrender = "part".
>
>
>
> If someone is wanting to submit a PR to remove the @altrender requirement
> to the feature, we would certainly look at it.
>
>
>
> b,chris.
>
>
>
> ------------------------------
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Bowers, Kate A. <kate_bowers at harvard.edu>
> *Sent:* Tuesday, March 08, 2016 5:16 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Any progress on AR1134
> (ingesting EAD <dimensions> and <physfacet>)?
>
>
>
> What are the next steps toward getting this bug fixed?
>
>
>
> I have just uploaded a document to
> https://archivesspace.atlassian.net/browse/AR-1134
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1134&d=CwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=ZiA4lKtFjjvXBp_jnGl60EM_epYBy-o_l1XqJtuMclc&s=WA1pOD-hlNR3C4LiqJXWMQMKvaWY7uuD6sewvznDQqw&e=>
>
> It includes:
>
> 1) Undesirable behavior (current behavior)
>
> 2) Desired behavior
>
> 3) Multiple screenshots from my testing
>
>
>
> Thanks!
>
>
>
> Kate
>
>
>
> *Kate Bowers*
>
> Collections Services Archivist for Metadata, Systems, and Standards
>
> Harvard University Archives
>
> kate_bowers at harvard.edu <megan_sniffin-marinoff at harvard.edu>
>
> 617.496.2713
>
> voice: (617) 384-7787
>
> fax: (617) 495-8011
>
> web: http://nrs.harvard.edu/urn-3:hul.eresource:archives
>
> Twitter: @k8_bowers
>
>
>
>
>
> *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 *Bowers,
> Kate A.
> *Sent:* Thursday, March 03, 2016 1:53 PM
> *To:* Archivesspace Users Group
> *Subject:* [Archivesspace_Users_Group] Any progress on AR1134 (ingesting
> EAD <dimensions> and <physfacet>)?
>
>
>
>
>
> I have been told that this issue is in Sprint 19, the current sprint, but
> the status is "icebox".  What does "icebox" mean?
>
>
> https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1134-3Fjql-3Dtext-2520-7E-2520-2522Dimensions-2522&d=CwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=ZiA4lKtFjjvXBp_jnGl60EM_epYBy-o_l1XqJtuMclc&s=ARHzzWuvH_v-yAPrcjOGhqtFBXBLvZBR0M8aHFmFrIc&e=>
>
> One of the reasons we ar particularly interested is that many EAD
> descriptions of photo collections make particularly heavy use of
> <physfacet> and <dimensions>.
>
> Thanks!
>
> Kate
>
>
> Kate Bowers
> Collections Services Archivist for Metadata, Systems, and Standards
> Harvard University Archives
> Cambridge, Massachusetts, USA
> voice: (617) 384-7787
> fax: (617) 495-8011
> kate_bowers at harvard.edu
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>

-- 

*Dallas Pillen*Assistant Archivist for Metadata and Digital Projects

  Bentley Historical Library <http://bentley.umich.edu/>
  1150 Beal Avenue
  Ann Arbor, Michigan 48109-2113
  734.647.3559
  Twitter <https://twitter.com/umichBentley> Facebook
<https://www.facebook.com/bentleyhistoricallibrary>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160308/c791b5aa/attachment.html>