Staff slips - Trillium - Notes on functionality
To support the new work For use at location, some new staff slips tokens has been added, and the edit options of the staff slips has been improved as well with the possibility to edit the layout using basic HTML.
The work is developed by National Library of Sweden and Index Data as the Klemming development team. Sorting of staff slips has also Stanford University been co-funding.
New staff slips token
Related JIRA: https://folio-org.atlassian.net/browse/UXPROD-5153
Edit staff slips using basic HTML
The existing plain layout functionality of patron notices in FOLIO do not leave sufficient options to do e.g. table layout, and do not have an option to have more advanced settings of the display in each cell of the table.
Related JIRA: https://folio-org.atlassian.net/browse/UXPROD-5250
In scope
Allow for columns or tables
Allow to crop large barcode images, by setting the hight and width of the image
Allow for aligning left, center, right in the different cells
Allow for the addition of containing boxes and lines
Option to fit to page - all content is contained to a single page.
How to set up staff slips using HTML
When you create your staff slip then go to Settings > Circulation > Staff slips, and then we here will use the Pick slip as an example
Select the Pick slip and view in detailed view - here as default Maintained as raw HTML is not enabled.
Then click the Edit button, and add a check mark in the option Maintained as raw HTML, and this functionality will be enabled. Notice the two buttons to the right, above the Template content.
Will display the list of tokens which can be added into the patron notice template. | |
Will preview the HTML layout with sample data. |
Notice this is not advanced use of the HTML5 and later versions of the Living Standard, but as the example below shows then you now definitely has many more options for better layout of your patron notice with this new functionality.
If you want to see a real life example of HTML coding written up by National Library of Sweden then read more here Basic HTML tagging of staff slips (Trillium work)
Sorting of pick slips
Pick slips (for page requests) did printing in a random order, which caused extra work for circulation staff that must sort manually the slips by location and then by call number before they can be pulled from their stacks.
Scope
Supporting server side sorting of page slips by Effective location and Shelving order (AKA Effective sort call number)
If there is no Shelving order, then the Title should be used instead.
Following has been implemented:
1:
Given: Multiple pages requests from locations assigned to servicepoint_1 + each item has a Shelving order,
When: The staff user clicks on "Print pick slips for servicepoint_1" from the Actions menu in the Requests app,
Then: A PDF is displayed with all the staff slips for that service point ordered as follows:
FIRST: Grouped by and sorted by Effective location (FOLIO name); ascending order (a-z)
THEN: Sorted by Shelving order; ascending order (a-z)
2:
Given: Multiple pages requests from locations assigned to servicepoint_1 + none of the items has a Shelving order,
When: The staff user clicks on "Print pick slips for servicepoint_1" from the Actions menu in the Requests app,
Then: A PDF is displayed with all the staff slips for that service point ordered as follows:
FIRST: Grouped by and sorted by; ascending order (a-z)
THEN: Sorted by Title; ascending order (a-z)
3:
Given: Multiple pages requests from locations assigned to servicepoint_1 + some items have a Shelving order, some do not have a shelving order,
When: The staff user clicks on "Print pick slips for servicepoint_1" from the Actions menu in the Requests app,
Then: A PDF is displayed with all the staff slips for that service point ordered as follows:
FIRST: Grouped by and sorted by Effective location (FOLIO name); ascending order (a-z)
THEN: Items with a Shelving order should be sorted on that field; ascending order (a-z)
THEN: Items without a Shelving order should be sorted by the title; ascending order (a-z)
Related JIRA: https://folio-org.atlassian.net/browse/UXPROD-4462
The sorting should also work for search slips but the scope of the ticket was only for pick slips and the unit tests only verify that it works for pick slips.
Links and more background documentation
Documentation on the technical solution can be found here on GitHub