Print

Print


Ah, I see.  So this would be a separate step we'd have to run our EAD through, then?  We already have the EAD Report Card built into our workflow; maybe we'll just add code to that.  It never occurred to me to do that, but since we're already using it and it sounds like it would be essentially the same approach ("an XSLT stylesheet, which is applied to the documents being validated to generate the test results") that might be the easiest thing.

Thanks!

Michele

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Wendell Piez
Sent: Thursday, March 13, 2014 10:57 AM
To: [log in to unmask]
Subject: Re: end punctuation in controlled headings

Hi Michele,

I mentioned oXygen only because it has good support for Schematron.
But since Schematron itself is an XSLT application, it's also possible, in principle, to run it anywhere you can run XSLT. (It works by running the Schematron schema through an XSLT pipeline that generates an XSLT stylesheet, which is applied to the documents being validated to generate the test results.) It's significantly more work to set up, of course -- if only because running Schematron bare-bones, you then get raw XML output, which you then have to transform again to have something to look at.

Oh, the best thing about Schematron? You get to write your own error messages. So your users have a chance of getting feedback, when validating their data, that is actually useful to them.

<rule context="unittitle">
  <report test="matches(.,'\p{P}$')">Yo! The system will add the punctuation!
    Remove the <value-of select="replace(.,'^.*(\p{P}+)$','$1')"/>
from the end of the <name/>!</report>
  </rule>
</pattern>

Cheers, Wendell


On Thu, Mar 13, 2014 at 10:30 AM, Michele R Combs <[log in to unmask]> wrote:
> Hi Wendell --
>
> Some of our workstations have a very old version of XMetaL which doesn't even know what schemas are, so this probably wouldn't help with those, but others do have Oxygen.  I'll check into this for the Oxygen ones, thanks!
>
> Michele
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] 
> On Behalf Of Wendell Piez
> Sent: Wednesday, March 12, 2014 12:36 PM
> To: [log in to unmask]
> Subject: Re: end punctuation in controlled headings
>
> Hi Michele,
>
> Regarding validation of content (including, for example, rules regarding punctuation) -- any particular reason why you can't use Schematron? It works well with DTD, XSD, RNG, you name it.
>
> Schematron (for those who don't know it) is essentially a "semantic wrapper" language for XSLT that simplifies building and applying XPath-based tests for your XML. You can test anything in the document you can see with XPath. Set it up with XSLT 2.0 and you have all the power of XSD for content checking, and then some -- content analysis, co-occurrence constraints, and so forth. So whatever your rules are regarding punctuation, Schematron will help you enforce them.
>
> Here's a Schematron that will tell you about any 'unittitle' elements that end with punctuation. Note that the test is in XPath 2.0:
>
> <schema xmlns="http://purl.oclc.org/dsdl/schematron" 
> queryBinding="xslt2">
>
>   <pattern>
>     <rule context="unittitle">
>       <report test="matches(.,'\p{P}$')"><name/> ends with punctuation</report>
>     </rule>
>   </pattern>
>
> </schema>
>
> If you are lucky enough to be editing your EAD in oXygen, you can set this up to validate in the background along with your schema. The "error" will show up as soon as you make it.
>
> Plus, the binding to the data is loose, so you can use Schematron whenever you need to in the workflow, use more than one, etc. etc.
>
> Cheers, Wendell
>
> On Wed, Mar 12, 2014 at 7:42 AM, Michele R Combs <[log in to unmask]> wrote:
>> We do include all proper MARC punctuation because we generate MARC 
>> records from our EAD.  So it saves us a step.
>>
>> One could also argue that if the @encodinganalog value for a given 
>> element is a MARC field (which it is in our finding aids), then it's 
>> proper to use MARC rules for those elements.
>>
>> I will also add that making sure people remember to include said 
>> punctuation is kind of a PITA.  If we were using the schema it would 
>> be easier to enforce but we're still using the DTD.  If you decide to 
>> go with it, you'd be several steps ahead if you find a way to enforce it upon data entry!
>>
>> Michele
>> ________________________________
>> From: Encoded Archival Description List <[log in to unmask]> on 
>> behalf of Ashley Knox <[log in to unmask]>
>> Sent: Tuesday, March 11, 2014 11:11 PM
>> To: [log in to unmask]
>> Subject: end punctuation in controlled headings
>>
>> This has probably been spoken about in the past, but now that so many 
>> EAD implementors are using data entry systems and not necessarily 
>> generating custom stylesheets, what might the consensus be on using 
>> end punctuation after controlled headings. Is there a strong reason 
>> to keep or get rid of it? I have heard arguments for both.
>>
>> As a digital collections department, we are stuck between a rock and 
>> a hard place in trying to standardize this. I'm seeing many 
>> digital/metadata heavy groups going away from the punctuation in 
>> metadata for digital objects (perhaps planning to allow for systems 
>> to control that still) and then EAD implementors creating finding 
>> aids with the punctuation.  I surveyed a few institutions that came 
>> to mind. I mostly see the punctuation kept. However, with something 
>> like DPLA, there is no end punctuation. I'm creating metadata and 
>> finding aids for both areas, but describing the same material, as in, 
>> a finding aid of correspondence with punctuated controlled headings 
>> and then a digital collection of the same correspondence with DC metadata with non-punctuated headings.
>>
>> We plan to implement ArchivesSpace and we don't really know an 
>> automated way to switch back and forth between formatting choices 
>> like this conveniently, so it would be great to go with something and 
>> stick with it. Right now, in our AT, we use end punctuation. I guess 
>> what matters is that we CAN include the punctuation at our 
>> institution if we want to and export/share our EAD that can easily be 
>> altered through stylesheets if a system we shared with opted against 
>> them. I still have a hard time grasping using the same headings in 
>> two different places at our own institution and including punctuation 
>> in one and not the other--with no real strong reason of why on 
>> either--while at the same time having no qualms with the fact that 
>> our library catalog obviously uses it and is where the argument 
>> begins. If someone can show me some examples of what they do and why, 
>> or why we shouldn't care about a small formatting issue that could 
>> also span across other fields too, I would appreciate it greatly. 
>> MARC 245 also uses end punctuation, but EAD finding aid titles do not? Is this a parallel issue that would show why punctuation doesn't matter?
>>
>>
>> DPLA – No Periods
>> http://dp.la/item/4696d87c59b75357b801aa9090df6780?back_uri=http%3A%2
>> F 
>> %2Fdp.la%2Fsearch%3Fq%3Dcar%26subject%255B%255D%3DBusiness%252C%2BEco
>> n
>> omics%2Band%2BFinance%26utf8%3D%25E2%259C%2593
>>
>> These finding aid/EAC/EAD examples/best practices say do 
>> include/instruct to use periods
>>
>> LC:
>> http://findingaids.loc.gov/db/search/xq/searchMfer02.xq?_id=loc.mss.e
>> a 
>> dmss.ms007005&_faSection=indexTerms&_faSubsection=controlaccess&_dmdi
>> d
>> =d5384e7
>>
>>
>>
>> SNAC:
>> http://socialarchive.iath.virginia.edu/xtf/search?sectionType=cpfdesc
>> r 
>> iption;f1-localDescription=College%20students;f2-localDescription=Gre
>> e
>> k%20letter%20societies
>>
>>
>>
>> OAC Practices - page 13:
>> http://www.cdlib.org/services/access_publishing/dsc/tools/docs/EAD_We
>> b
>> _Templates.pdf
>>
>>
>>
>> Northwest Digital Archives Best Practice Guidelines
>>
>> Page 25 – their systems adds it in for them, so they don’t put it in 
>> manually
>>
>> _____________________________________________________________
>>
>>
>> DACS 2nd Edition says to follow AACR2 or RDA, but then the examples 
>> don't actually use any end punctuation.
>>
>> http://files.archivists.org/pubs/DACS2E-2013.pdf
>>
>>
>> PAGE 32--General Rules
>> 2.6.4 Record the name(s) of the creator(s) identified in the name 
>> element in the devised title of the materials using standardized 
>> vocabularies (e.g., Library of Congress
>> Authorities) or with rules for formulating standardized names, such 
>> as those found in AACR2, ISAAR(CPF), or RDA.
>>  Hamilton, Alexander, 1757-1804
>>  Title: Alexander Hamilton papers
>>
>> Lyon, Phyllis
>> Martin, Del
>>  Title: Phyllis Lyon and Del Martin papers
>>
>> Richardson, James Burchell
>>  Title: James Burchell Richardson family papers
>>
>> Schramm family
>>  Title: Schramm family papers
>>
>> Wharton, Edith, 1862-1937
>> Fullerton, William Morton, b. 1865
>> Title: Edith Wharton correspondence with Morton Fullerton
>>
>> Bollingen Foundation
>>  Title: Bollingen Foundation records
>>
>> United States. Bureau of Insular Affairs
>>  Title: United States Bureau of Insular Affairs records
>>
>> Irvine Company
>> University of California (System). Regents.
>> Title: Land agreements between the University of California and the 
>> Irvine Company
>>
>>
>> PAGE 87
>> Finally, the names of these entities must be rendered in a 
>> standardized form using standardized vocabularies (e.g., Library of 
>> Congress Authorities) or with rules for formulating standardized 
>> names such as those found in AACR2, ISAAR(CPF), or RDA to facilitate 
>> the retrieval of information across descriptions, systems, and 
>> institutions.
>> _________________________________________________________________
>>
>> And FINALLY, EAD3 Gamma has an example on page 243 of a subject 
>> heading encoded and DOES include end punctuation.
>> http://www2.archivists.org/sites/all/files/gammaEAD3TagLibrary.pdf
>>
>> __________________________________________________________
>>
>>
>> ArchivesSpace members (examples of current EAD examples):
>>
>>
>> http://www.archivesspace.org/General%20Members
>>
>> end punctuation
>> http://www.library.gatech.edu/archives/finding-aids/search?browse-all
>> =
>> yes;expand=subject
>>
>> http://www.uic.edu/depts/lib/specialcoll/services/rjd/findingaids/AFS
>> C
>> f.html
>>
>> http://etext.ku.edu/view?docId=ksrlead/ksrl.kc.abrahamburld.xml;route
>> =
>> ksrlead;brand=ksrlead;query=
>>
>> http://www.nmu.edu/sites/DrupalArchives/files/UserFiles//MSS-016.html
>>
>> http://www2.lib.unc.edu/mss/inv/l/London_Family.html (nonmember)
>>
>>
>> no end punctuation
>> http://proust.library.miami.edu/findingaids/?p=subjects/subjects&char
>> =
>> W
>>
>> http://archon.brandeis.edu/index.php?p=collections/controlcard&id=77
>>
>> http://digital.library.pitt.edu/cgi-bin/f/findaid/findaid-idx?c=ascea
>> d
>> &cc=ascead&rgn=main&view=text&didno=US-PPiU-ais198113
>>
>> https://www.library.unlv.edu/speccol/ead/1996-08_Duncan.xml
>>
>>
>> Thanks,
>>
>>
>> Ashley Knox
>>
>> Digital Projects Librarian
>>
>> University of South Carolina Libraries
>>
>> [log in to unmask]
>>
>> (803) 777-0735
>>
>> http://library.sc.edu/digital
>
>
>
> --
> Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic 
> publishing Eat Your Vegetables 
> _____oo_________o_o___ooooo____ooooooo_^



--
Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^