SobekCM Repository Community Help | |
Project Home | User Help | Technical Help | Download Center | Code Details | mySobek Home |
SobekCM Version 4.10.2 Release Notes
Release notes for version 4.10.2 which was released on September 4th, 2017. SummaryVersion 4.10.2 included a number of architectural changes, which continue the development of the open architecture and plug-in support. This includes, among other things, the following categories of changes:
The full list of changes appears below. Version 4.10.2 Change Log
Builder UpdatesThe builder application received many updates primarily focused at removing as most HTML creation from the builder, increasing the support for builder plug-ins, and additional search engine optimization features. In addition, several bug fixes and configuration updates were also included. In previous versions of SobekCM, the builder would include the SobekCM HTML rendering library and would directly write HTML for canned browses, item views, and other outputs. In the new version, all the HTML empty frames and item level pages are pulled from the web application directly. The pages that require some HTML generation are added with an empty frame pulled from the web application. The new builder no longer links to the SobekCM_Library DLL, after moving several stored procedures between database gateway classes. This allows more of the overall look and feel of the generated pages to be controlled through the plug-ins in the web application and configuration. The builder assists with overall search engine optimization by building static browse HTML files, RSS feeds, and static pages for each item to allow item metadata and files to be served quickly for search engine requests, without building the full item in memory. These item level static pages are now pulled from the /robot item viewer from the web application, but this can be changed via configuration or plug-ins. This new version includes a complete rewrite of the code that created the non-item pages for search engine indexing, which includes the sitemaps and rss HTML pages. In addition, sitemap creation was corrected for multi-instance builders and a new sitemap collection file is being created. On a daily basis, a schedulable builder module is called to recreate all the sitemaps and aggregation pages daily. Additional code reorganization prepares to move some existing modules into plug-ins and increases ease when creating plug-ins. For example, the FDA ( Florida Dark Archive ) module was moved into its own code and the database calls moved into its own database gateway. Much of the base builder codes ( like the interfaces and abstract classes for the modules ) was moved out of the Builder library and into the Core code. This allows builder modules to be created that don't need to reference the Builder Library. This early requirement was making testing difficult due to circular redundancies in testing. Some final code reorganization moved much of the start-up functionality into schedulable builder modules which can be enabled or disabled in the database. The ability to schedule the tasks will be necessary when the builder is moved into a service running non-stop. The following additional builder changes were also included:
Results Viewer Configuration and Plug-InsA new architecture was created for the different result viewers, including a configuration file and reader and new tables in the database connecting aggregations with their result viewers. This included a code restructure of the existing result viewers and updates to the result viewer factory. In addition, the types of results views included in a collection, including the order and the default view, are now stored in the database. Plug-ins for new result viewers are supported by the architecture, and a new timeline result viewer plug-in is currently under development. Item Viewers and Item LayoutsIn previous versions of SobekCM, the general look and feel of the item viewer was static. Over the last year, the item viewer plug-ins were introduced, which allowed a plug-in to alter the main viewer portion of the page when viewing an item. This new version builds upon those changes, adds the ability to control the overall look and feel within the item viewer in your instance by utilizing item layout configurations, and corrects a number of miscellaneous issues with the item viewers. A new architecture for inserting metadata into the HTML head on the digital resource pages was added allowing better search engine indexing while simultaneously increasing the ability to customize the metadata included. Item layouts can now be utilized to alter the overall look and structure of the page that displays the individual digital resources. Layouts are defined within the configuration files and reference HTML layout files with all the stub HTML. Within the configuration and html file, sections are defined that can then have objects referenced in the configuration to have complete control over what item data is written in each section. The layouts can be chosen at the item level and individual item viewers can override the current item layout. This allows the quality control tool and page-turner, for example, to not utilize the left navigation bar at all. Several updates support increased search engine optimization with the items. A new robots item viewer was created to provide the raw HTML for the builder to use when creating the static HTML source files for quick search robot requests. In addition, a new configurable architecture was added to allow the metadata written in the HTML head, and subsequently indexed by search engines, to be customized. The web and builder no longer keep a complete list of every item in memory. For each (apparently valid) item request, a database check is performed. This also allows for better error to be provided. The errors include an invalid BibID requested and can even suggest an alternate VID if necessary. The main item writer now uses these codes from the MidTier engine as well. The following additional item viewer changes were also included:
HTTPS (SSL) SupportSupport for HTTPS/SSL access was updated and a new content delivery network is available for all the static files over HTTPS. Within the system-wide settings, the option to choose the static resource configuration source is now a special drop-down box, which lists all the existing static resource configurations from the config folders. A new HTTPS static resource configuration file is now included that points to https://cdn.sobekdigital.com for all the digital resources, which utilizes our corporate certificate. The world-wide content delivery network was enabled for that URL as well, allowing the content to be served from over 30 locations worldwide, for best performance. Two additional minor updates were also included to finish the HTTPS/SSL support:
Item Management Updates
Miscellaneous
|