[Archivesspace_Users_Group] Formatting Links in Scope Note

[Andrew Morrison]

You can see the relevant section of code here:

https://github.com/archivesspace/archivesspace/blob/cfc0a4943e50706ed4c073241de49a06f5d5e295/public/app/views/shared/_result.html.erb#L14-L31

The main points to note are that the scope and contents note will only 
be used if there is no abstract. And, whichever is used, if it contains 
more than a preset limit (500 characters), it will be truncated. In 
order to do so safely (without risking creating invalid HTML by, say, 
truncating in the middle of a bullet-point list) it converts to plain 
text (strip_tags). Hence your links won't work whenever what is 
displayed in the search results ends with an ellipsis (...) indicating 
the truncation has been applied.

You could put your links to PDFs in abstracts, that way only they would 
displayed in search results. Or, if you are using 2.6.0 or better, you 
could increase the limit by setting /abstract_note_length/ in the config 
file to something higher than 500. Or override that template completely 
in a plug-in.

Andrew.


On 01/04/2020 21:47, Hoffner, Bailey E. wrote:
>
> Hello All,
>
> We are currently implementing ArchivesSpace at the University of 
> Oklahoma Libraries and are taking a dynamic, top-down approach to the 
> work: collection level records for all, then ingesting deeper 
> component records, for our thousands of collections.
>
> As a temporary measure to get our users out of our current online 
> finding aid registry and into ArchivesSpace, we are dropping links 
> into the top of the scope and contents notes that will guide 
> researchers to the current full PDFs – these will be removed once the 
> collections are fully described in ArchivesSpace but it’s a necessary 
> step for us at this time.
>
> So far, the links show up at the top of each collection level record 
> and are also clickable links in the preview version of the collection 
> record that comes up when users search. Except for one of them that is 
> oddly not formatting the same way (see below). The successful and 
> unsuccessful examples look exactly the same on the staff interface and 
> I’ve tried yanking out all the scope text and turning it to plain text 
> – no luck. Any tips?
>
> Thanks!
>
> -Bailey
>
> Successful:
>
> A screenshot of a cell phone Description automatically generated
>
> Not Successful:
>
> A screenshot of a cell phone Description automatically generated
>
> Bailey Hoffner, MLIS
>
> Metadata and Collections Management Archivist
>
> University of Oklahoma Libraries
>
> 405-325-1566
>
>
> _______________________________________________
> 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/20200402/cd6773e9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 88255 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200402/cd6773e9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 92481 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200402/cd6773e9/attachment-0001.png>