[Archivesspace_Users_Group] Publish All workflows

Thu Sep 13 11:27:56 EDT 2018

Yes: I think publish/publish-all was a design error that has caused much confusion for users. 
First, “publish” is a verb that’s being used as an attribute. It should have been “public” . 
And the “publish all” button, which is a verb, just made if more confusing. 

In most cases, for most libraries, public is a better default. 
If public was the default and the checkbox was “internal” , there would be less need for a button to change the status of all children to “publish” . ( Maybe there is a way to make the defaults for different records configurable, or make the defaults for different kinds of notes different. ) 

But there is still a use case for a “publish” (as a verb) button, that would trigger PUI indexing and perhaps some other actions. 
As it works currently, incomplete records that are correctly marked to be public go out to the PUI and OAI endpoints. 
Changing the finding aid status to complete does not trigger any action. 

So perhaps there should be a “publish” button that changes finding aid status, creates an event record that indicates that the resource was published, and triggers PUI indexing. 

— Steve Majewski

> On Sep 13, 2018, at 9:54 AM, Kennedy, Nancy <KennedyN at si.edu> wrote:
> 
> Thanks, Noah, Brian. 
>  
> Noah – re: “we keep track of the publication status of a finding aid using the Finding Aid Status field” .  We do the same thing, using Finding Aid Status to drive the EAD export.
>  
> Using FA Status has worked pretty well… except that screen labels like “publish?” leads to some (I’d say legitimately!) confused users.  Especially when there is, say, a network slow down and people try to troubleshoot by clicking on lots of inviting buttons… like “publish all”.  We try to train everyone on what “Publish?” checkbox means, but it’s easy to confuse.
>  
> I’ve considered relabeling the ‘’Publish?” field to something like ‘External Audience’ … but I don’t want to move us far afield form the core archivesspace code/documentation. If I change the display label, my users will understand that we mean audience and not status .  The problem is changing labels means our views will drift away from the main core archivesspace documentation, screencasts etc.  And the term ‘publish” appears in many places. Label translation seems like a band aid (and not a very good one).   A 2nd element specific to audience would probably be much better than a label change.
>  
> Nancy
>  
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Brian Thomas
> Sent: Thursday, September 13, 2018 9:22 AM
> To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] Publish All workflows
>  
> Hi all,
> I cannot speak to Noah’s questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been.
> Thanks,
>  
> 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 <x-msg://1/bthomas@tsl.texas.gov>
> tsl.texas.gov <http://tsl.texas.gov/>
> <image001.png>
>  
> 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 Noah Huffman
> Sent: Thursday, September 13, 2018 8:10 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] Publish All workflows
>  
> Hi Nancy,
>  
> We ran into a similar problem to the one you describe—folks accidentally clicking “publish all” when a resource record contained some archival objects that should remain unpublished.
>  
> To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking “publish all.”  We also have some scripts that batch export EADs and publish all at the same time.  Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding.  This isn’t a fail-proof solution, but has helped mitigate the problem of publishing things we didn’t intend to publish. We’re also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD.
>  
> RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.).  That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another.
>  
> I’m also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource.
>  
> -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/ <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.duke.edu%2Frubenstein%2F&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C6e19455dbaae4ca5842408d6197a40da%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636724410210278412&sdata=ITwIeJKvxl3wQ25VbQtDPbpEJTyDLV1fvhdXXSBOJxk%3D&reserved=0>
>  
>  
>  
>  
> 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 Kennedy, Nancy
> Sent: Thursday, September 13, 2018 8:21 AM
> To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org <mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> Subject: [Archivesspace_Users_Group] Publish All workflows
>  
> Hello all,
> We have had a few cases where users hit the ‘Publish All’ button for collections containing ‘internal’ archival_objects or notes (i.e. where the EAD @audience is ”internal”). 
>  
> I wonder how other institutions handle collections with ‘internal’ content?  What workflows or fail-safes do you use?  Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. 
>  
> In our situation, an ideal solution would be to separate ‘publish’ into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external).  Which would of course be quite involved.  It does however seem like it would be helpful all around if ‘Publish?’ vs ‘Audience?’ could be separate elements, so that I can protect internal audience material from publishing.
>  
> What do you all think?
>  
> Nancy
>  
>  
> Nancy Kennedy
> Smithsonian Institution
> kennedyn at si.edu <mailto:kennedyn at si.edu>
>  
> _______________________________________________
> 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/20180913/cc240788/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6091 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180913/cc240788/attachment.bin>