[Archivesspace_Users_Group] DACS 7.1.6 equivalent in ArchivesSpace
Kari R Smith
smithkr at mit.edu
Wed Nov 16 12:27:46 EST 2016
Hi all,
Has there been a fix for having the EAD ID show along with the Resource title when selecting a resource for Background Printing jobs?
We are finding that we have many collections that begin, Massachusetts Institute of Technology, Office of the Pick Your Choice of Offices, Dean of the office mentioned. Because the Dates (which often distinguishes one collection from another) don’t display in the Resource title, we are faced with just printed all of the them and then sorting out the single collections we were trying to Print the finding aid for.
Kari
Kari R. Smith
Digital Archivist, Institute Archives and Special Collections
Massachusetts Institute of Technology Libraries
617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Wednesday, November 16, 2016 11:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DACS 7.1.6 equivalent in ArchivesSpace
Christine, Cheri:
I’ve been meaning to make a few changes to the XSL-FO Stylesheet that ASpace uses to create PDFs, and it seems like this should feature request should be in the core code. I doubt I’ll get around to this work until late December / early January, but I’d be happy to submit a pull request if this is added to JIRA.
In the meantime, there are a couple of things going on here:
1. As Christine notes, there’s a section in the file already that will display series-level unitid values if that section is uncommented (you can find that section in the “<xsl:template match="ead:did" mode="dscSeriesTitle"” template). To uncomment, you’ll need to remove the “<!--“ from the beginning of the section, and the “-->” at the end of the section. Ideally, I’d like to change this so that you could just pass a different parameter to the file to control that behavior so that folks won’t have to edit the XSL file itself.
2. For the lower-levels, you’ll need to make sure that the unitid elements are called by the parent ead:did template, but right now that’s not happening. At the very end of the file, you’ll find the following template:
<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]) > 1) and (string-length(ead:unitdate[1]) > 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>
To see your unitds in the output, change that template to this:
<!-- 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]) > 1) and (string-length(ead:unitdate[1]) > 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:unitid" mode="dsc"/>
<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>
Now, if you have a unitid of “xyz” and create a PDF file, it’ll display as “ID: xyz”. If you don’t want that label, you can remove “mode=’dsc’” from the highlighted line above, and you’ll just get “xyz” in the output.
I hope that helps,
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 Christine Di Bella
Sent: Wednesday, 16 November, 2016 10:01 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] DACS 7.1.6 equivalent in ArchivesSpace
Hi Cheri,
From what you describe, Component Unique Identifier is the best field in which to record this information. This field is part of the standard EAD export (it exports as <unitid>), so it is available for use in the PDF. The PDF layout and formatting is controlled by an XSLT stylesheet (called as-ead-pdf.xsl) that comes with ArchivesSpace and is stored on your server in the archivesspace/stylesheets folder. The stylesheet is editable and customizable, if you have parts that you want to display differently from how it comes “out of the box”.
There is code already in the stylesheet that is commented out that can be uncommented to add unitids to higher level components. Does anyone on the list have a stylesheet they can share that displays unitids at lower levels? Or can you point Cheri in the right direction for how to modify hers?
Christine
Christine Di Bella
Community Outreach Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)
[cid:image003.png at 01CE734E.FD759D30]
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 Cheri Crist
Sent: Tuesday, November 15, 2016 12:35 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] DACS 7.1.6 equivalent in ArchivesSpace
Hi list,
I'm finding that somewhere in the annals of time, individual pieces of ephemera were given museum object numbers in TMS, and these numbers are written on the items. I'm wondering if anyone out there has a best practice for recording these numbers in AS. I thought recording the TMS number in the Component Unique Identifier field at item level would work, but it doesn't show up in the pdf. (It does show in the public interface, however.) What have other people done?
Thanks,
Cheri
Cheri Crist
Project Archivist
Richard and Ronay Menschel Library
George Eastman Museum
900 East Ave.
Rochester, NY 14607
ccrist at eastman.org<mailto:ccrist at eastman.org>
(585)271-3361 ext. 280
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/a4f158ec/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12360 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/a4f158ec/attachment.png>
More information about the Archivesspace_Users_Group
mailing list