This page expects to be accessed as https://cookjools.github.io/bl_universal_viewer_demo/INDEX_TO_MANUSCRIPTS_FOR_ALEXANDER.htm
|
|
|
|
Demo Universal Viewer embedded in a web-page similar to standard BL UV pages (hint: right click to open in separate tab) |
Demo Universal Viewer (hint: right click to open in separate tab) |
Demo Mirador (hint: right click to open in separate tab) |
|
2 |
EAP000_1_2 |
add_ms_27261 |
https://cookjools.github.io/bl_universal_viewer_demo/add_ms_27261/embedded_bl_style_uv.html |
||
|
3 |
EAP000_1_3 |
i_o_islamic_3562 |
https://cookjools.github.io/bl_universal_viewer_demo/i_o_islamic_3562/embedded_bl_style_uv.html |
||
|
4 |
EAP000_1_4 |
or_16919 [WRONGLY FOLIATED] |
|
|
|
|
5 |
EAP000_1_5 |
add_ms_25900 |
https://cookjools.github.io/bl_universal_viewer_demo/add_ms_25900/embedded_bl_style_uv.html |
||
|
6 |
EAP000_1_6 |
i_o_islamic_550 |
https://cookjools.github.io/bl_universal_viewer_demo/i_o_islamic_550/embedded_bl_style_uv.html |
||
|
7 |
EAP000_1_7 |
or_2265 |
https://cookjools.github.io/bl_universal_viewer_demo/or_2265/embedded_bl_style_uv.html |
|
|
|
|
Demo Universal Viewer embedded in a web-page similar to standard BL UV pages (hint: right click to open in separate tab) |
Demo Universal Viewer (hint: right click to open in separate tab) |
Demo Mirador (hint: right click to open in separate tab) |
|
19 |
EAP000_1_19 |
io_islamic_3682 |
https://cookjools.github.io/bl_universal_viewer_demo/io_islamic_3682/embedded_bl_style_uv.html |
JPEG 2000 (jp2) images ingested into EAP (as TIFFs) are stored on the EAP IIIF server (AWS) under folder /EAP000/.
For example, the first image for EAP000_1_2 (i.e. add_ms_27261) can be viewed as JPG using this IIIF-compliant URL: https://images.eap.bl.uk/EAP000/EAP000_1_2/1.jp2/full/full/0/default.jpg .
The associated info.json file is at https://images.eap.bl.uk/EAP000/EAP000_1_2/1.jp2
The IIIF manifests are created by a PHP script create_tei_facsimile_element_from_info_json_files.php. That script is run by Julian who then uploads the manifest onto his Github Pages using Github Desktop: for example, https://cookjools.github.io/bl_universal_viewer_demo/or_2265/script_created_manifest.json
The script draws data from the info.json files for each of the images and combines that with data set up in an XML file which is exported from an Excel file (one per manuscript). In that Excel/XML "manifest definition" file, Julian manually inserts the manuscript metadata, defines the ranges that make up the Index tab of UV, and assigns custom labels and an optional description for each canvas or image in the sequence (information that is displayed bottom right, below the BL logo when the user clicks About This Item).
E.g. https://cookjools.github.io/bl_universal_viewer_demo/add_ms_27261/embedded_bl_style_uv.html
These are constructed from a template based upon a "standard" BL Libsafe/Universal Viewer page such as that for Add MS 35021 (Bach autograph): https://access.bl.uk/item/viewer/ark:/81055/vdc_100052141780.0x000001
They all use a custom BL config file hosted on our Github Pages https://cookjools.github.io/bl_universal_viewer_demo/custom_uv_config.json which contains very few modifications from a standard BL config file (specifically https://api.bl.uk/configuration/universalviewer/v2/ark:/81055/vdc_100052141780.0x000001 ; which is that associated with Add MS 35021).
For the embedded manifest these HTML pages point at one of our manuscript-specific, script-created manifests, also hosted on our Github Pages (see listing above). The HTML pages themselves also reside on our Github pages.
Click Exit Full Screen (bottom right) to see the information around the embedded Universal Viewer.
See https://www.exhibit.so/exhibits/K6u3yIzB1ADlHg6rIsMZ where you will need to supply a password: 28SEPT2022xxx
To edit the Exhibit you need a different link: https://www.exhibit.so/exhibits/edit/ncVALyVv1rb60V74kVWC
The manifest supplied to Exhibit to get going with this was https://cookjools.github.io/bl_universal_viewer_demo/add_ms_27261/script_created_manifest.json .
Unfortunately, since the Exhibit is stored with St Andrews I know of no way of modifying this, if we wanted to use a different manifest. (If one only wanted to move the images to a different server this might not be a problem since it looks as if Exhibit sotrylines access images via named canvases in a UV manifest (and do not work directly with URLs for images on a IIIF server). One would have to recreate the entire Exhibit.so storyline as far as I can see. Another possibility might be to contact the UV developer, Edward Silverton on ed@mnemoscene.io , or via Adi – and to ask for help applying behind the scenes changes to an Exhibit page.
I have created a mockup HTML version of that Exhibit storyline on my Github pages with all the .js and .css files served from there rather than from Exhibit itself. See https://cookjools.github.io/exhibits/K6u3yIzB1ADlHg6rIsMZ . This serves up an .html page K6u3yIzB1ADlHg6rIsM.html which is equivalent to page at https://www.exhibit.so/exhibits/K6u3yIzB1ADlHg6rIsMZ).
Creating this mockup Exhibit involved making numerous changes to the source code served up by www.exhbit.so. Firstly, removing _ from the start of any folder or file name (which Github Pages seems to object to) and making corresponding edits (_next becoming next) in K6u3yIzB1ADlHg6rIsMZ.html and also in ./next/static/chunks/main-02d79fe8c2a509ed.js and …/webpack-f31e6168c6209b9c.js . To work out which files were needed, I watched the console browser complaining about not being able to load various .js or .css files and in each case saved the file from https://www.exhibit.so/ into the equivalent location under /cookjools.github.io/ .
This demonstrates in principle how one might replicate an Exhibit storyline (as HTML with its own JS and CSS) without having it served up from www.exhibit.so. It would enable one to modify the JSON within the page to use a different manifest, or different canvases, and to modify the annotations. Of course this is much easier and safer to do on Exhibit itself but it would provide a possible means of dealing with problems with an Exhibit if we were to delete, rename, or move to a different URL the underlying IIIIF manifest (say from my Github pages to a more permanent BL URL).
See https://cookjools.github.io/bl_universal_viewer_demo/add_ms_5600/embedded_bl_style_uv_LOCALISED.html
The HTML for this pages contains URLs such as https://cookjools.github.io/bl_universal_viewer_demo/UVR7/build/uv-2.0.2/lib/embed.js which point to embed.js on Github pages rather than to https://access.bl.uk/UVR7/build/uv-2.0.2/lib/embed.js The Github pages files are mostly identical to the equivalent files on access.bl.uk.
We have modified bundle.min.js to reverse the conventional BL order in which groups of items in the right-hand metadata panel are displayed. About this page (canvas level) now appears at the top, followed by About this part (range level), and finally About this manuscript (so-called manifest-level).
We have also modified iiif-metadata-component.js to include some code to vary the display of items class ‘value’ in the right-hand metadata panel. In the example manifest, we have inserted some text in Tibetan which the script should cause to be rendered in an extra-large font (so that the Tibetan is legible). In fact, we have now found a cleaner way of having Tibetan characters rendered in an extra-large font using pure CSS (with no need for any JQuery run at just the right time) – these changes are made defining a special “Tibetan” @font-face in theme.css within folder ./UVR7/build/uv-2.0.2/themes/uv-en-GB-theme/css/uv-seadragon-extension.
See https://bequessel.github.io/webpages/embedded_bl_style_uv_LOCALISED.html . This is a further customized version of the UV served from BQ’s Github pages.