Nothe distributed modules all use OpenSeadragon as the default viewer. Universal Viewer is added as a module ( -KM/Omeka-S-module-UniversalViewer). I believe UV was initially distributed as part of the IIIF Server module but then the two were separated.
If the template file is not present in your theme directory, Omeka takes the default one inside application/view/. So if you want to customize it, just copy it in your theme at the good place, and modify it. This is the same for the views created by the modules.
Ideally, the Universal viewer (and the other viewers I just published : Mirador and Diva) should be used by default when it is an image or an iiif, like it is with the pdf viewer, or the OpenDocument viewer. But it has some impact on other parts of Omeka S, so currently, they are only a view helper that can be added by theme creators.
Universal Viewer is a module for Omeka S that integrates UniversalViewer,a unified online player for any files, so it can display books, images, maps,audio, movies, pdf, epub, 3D, youtuben and anything else as long as theappropriate extension is installed. Rotation, zoom, inside search, etc. may bemanaged too.
The Universal Viewer was firstly developed by Digirati for the Wellcome Library,the British Library and the National Library of Wales, then open sourced(unlike the viewer of Gallica, the public digital library built by the Bibliothque Nationale de France,based on Mirador, which is sold to its partners).
For v3, an external repository was used in order to include the last versionof OpenSeaDragon, the main component that manages the zoom viewer (used in otherIIIF viewers), in order to manage IIIF v3. Run this command inside therepository of this external repository, then copy "dist" in directory "asset/vendor/uv3":
If you need to display big images (bigger than 1 to 10 MB according to yourserver, your network, and your users), use an external image server, or createtiles with Image Server. The tiling means that big images like maps and deeppaintings, and any other images, are converted into tiles in order to load andzoom them instantly.
The display of 3D models is fully supported by the widget and natively managedsince the release 2.3. 3D models are managed via the threejs library.Nevertheless, see the readme of the module Three JS Model viewer for somepossible additional requirements and the supported formats.
This Omeka S module is a rewrite of the Universal Viewer plugin for Omeka byBibLibre with the same features as the original plugin. Next, it was separatedinto three modules, the IIIF server, the Image server and the player Universal Viewer.
Omeka is a Digital Scholar project, originally launched at the Roy Rosenzweig Center for History and New Media with funding from multiple organizations. Omeka's name and logo are registered trademarks of Digital Scholar.
Take advantage of the universe of IIIF-compliant viewers (and other tools), each with different features and benefits. You can try out some of the most popular options here, or explore more on Awesome IIIF, a community-built compendium of all things IIIF managed on GitHub.
An open-source embeddable Viewer. Elegant and contemporary, Glycerine Viewer is implemented in Vue 3. Supports IIIF Presentation API for basic and properties recipes and provides a comprehensive annotation feature set.
SAS software is not required to view or use NHANES data. NHANES practice is to release data as SAS transport files, which can be read directly by a number of applications. However, for any application that cannot read transports directly, SAS offers a free data viewer. Datasets can be opened with the SAS viewer and saved as a CSV file that can be opened by other software applications.
The SAS Universal Viewer is a freely distributed application for viewing and printing files that were created by SAS. The Viewer provides a quick and convenient way to view SAS datasets, catalogs, transports, JMP files, HTML files, and all text-based files without invoking SAS, or even having SAS installed on your computer.
For guidance on performing common operations, such as filtering data , saving, and copying and pasting to other applications, with the SAS Universal Viewer please see the Performing Common Tasks with SAS Universal Viewer in the SAS Universal Viewer Documentation.
SAS and all other SAS Institute product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. Other brand and product names are registered trademarks or trademarks of their respective companies.
Universal Viewer is a community-developed, IIIF-based viewer that has similar functionality to Mirador. Any IIIF content can be loaded and displayed in Universal Viewer. This recipe uses version 4 of Universal Viewer and integrates it into CONTENTdm in the same way as the other IIIF-based viewer recipes.
The design of this recipe is simpler than the Mirador recipe because it loads the Universal Viewer application from a public content delivery network called jsDelivr rather than serving it directly from CONTENTdm. The files used in this recipe can be viewed and downloaded from the CONTENTdm Cookbook download portal under the Universal Viewer section.
The basis for this recipe will be a standard Custom Page which will be the container for Universal Viewer (see Create a custom page for more information). This HTML page has inline CSS styling to clear all margins and padding.
Download the uv.html custom page file for this integration. You can modify this HTML file as you see fit. For example, if you would like to display a different page title when Universal Viewer loads, edit the title in the YAML header at the top of the HTML code.
Upload your uv.html file in the Website Configuration Tool on the Global Settings > Custom > Custom Pages dialog using the manage files tool. This recipe assumes the HTML file is uploaded at the top level of the file structure (not in a subdirectory) and the file is named uv.html. If you rename the file you will also need to modify the JavaScript file used in step 2.
If you have no other custom JavaScript running on your website, upload the uv-cp.js file in the Website Configuration Tool on the Custom > Custom Scripts dialog. If you already have a JavaScript file added on the Custom Scripts page, you will need to modify that JavaScript file and copy the entire contents of uv-cp.js into the main custom JS file for your CONTENTdm site. The code in uv-cp.js is contained in a single function so can safely live alongside other JavaScript code. If you are using the Load multiple JavaScript files recipe, you can add uv-cp.js to your list of files to be loaded.
So far we've confined ourselves mostly to the IIIF Image API. Tools like OpenSeadragon and Leaflet sit on top of the Image API to give you zooming behaviour, but hat if you want all the richness of navigating structured collections: providing information and metadata to your users, tables of contents, and annotation?
The Presentation API gives you the tools to model these features of your content, and the Universal Viewer and Mirador are "full IIIF viewers" in the sense that they manifest this content for the user.
The UV has been developed as an open source tool by the British firm Digirati for use in the British Library's IIIF environment. It takes in a manifest or collection and gives you a window into its content so you can view its metadata and navigate it in various ways.It is available on npm and has many examples at the link above.
Mirador grew out of the needs of Art History and Manuscripts scholars at Stanford University and has grown through a multi-institutional collaboration with Harvard University and about 2 dozen contributors from around the world. In addition to viewing, it provides configurations for saving state, creating annotations through your backend, and comparison of multiple object from different institutions in a windowed workspace.
Once you have an image server running, you can create Presentation API "manifests" that point to those resources and provide enriched structure and presentational information to viewers like Mirador and UV. Many institutions generate their presentation manifests from existing institutional metadata to show their users. Others create them by hand.
The National Library of Medicine (NLM) is pleased to announce the implementation of the Universal Viewer for examining the thousands of digitized texts on the Digital Collections web site. Universal Viewer is an open-source community-supported software developed by Digirati for the Wellcome Library and the British Library.
The NLM Digital Repository Working Group selected Universal Viewer after an in-depth software evaluation. Universal Viewer fits easily with the existing applications Digital Collections uses to present high-quality page images through the International Image Interoperability Framework (IIIF), Loris image server and Blacklight discovery layer.
Within the Universal Viewer, users can zoom in, zoom out and rotate the page images (see Figure 2). Settings that the user may define include enabling the navigator (arrow), two-page view, mouse click to zoom and preserve zoom.
Another feature available in the new viewer is search and retrieval of keywords (see Figure 3) at the page level, which takes advantage of the full indexing of texts in the Digital Collections repository.
Sectra UniView solves the problem with information trapped in isolated department silos by image-enabling the EMR. It does this either thanks to its advanced integration capabilities, by using secure URL calls, or by embedding the viewer directly in the EMR.
As part of the Sectra Enterprise Image Management infrastructure, Sectra UniView complies with the same high standards for safety, security, and availability as the other modules included in the enterprise platform. For instance, no patient data is cached on clients, secure protocols are used for communication that ensure safe and secure information handling, and the solution supports authentication and authorization via federated login methods. In addition, Sectra UniView supports clinical access control with patient lock, block, and break glass functionality.
3a8082e126