Table of Contents

RIMMF Version 1: Changes

This page tracks the changes made in each RIMMF release (newest first).
Follow this link for a list of problems that have not been resolved.

Release 12.9.4, Update 12.11.25


Work begins on RIMMF2 (October 1, 2012)

We will still fix bugs in RIMMF1, but RIMMF2 will be the focus for new functionality.


Release 12.9.4, Update 12.10.4

Release 12.9.4, Update 12.9.5

Release 12.9.4

Release 12.8.20

Release 12.6.22, Update 120630

Release 12.6.22

FIXES

Release 12.4.23

CHANGES

FIXES


Release 12.4.18

CHANGES

FIXES


Release 12.4.13

CHANGES


Release 12.4.11

Note: No changes to any tables in this update

CHANGES

FIXES


Release 12.4.09

CHANGES

FIXES


Release 12.3.30

CHANGES

FIXES


1)
if you have customized the elements, vocabularies, and/or vocab terms distributed with the program
2)
This is based on Deborah's strategy that when cataloging a new resource, one should typically begin with the Manifestation, then create the Work, and finally the Expression. This strategy is explicit in the menu options that appear when a RIMMF Identifier is right-clicked. Perhaps, we should have named this 'Build MWE' but could not figure out how to pronounce that.
3)
when compared to the current MARC workflow; Note that you can generate the records in the M-W-E cycle quite quickly if you start off with a good store of templates, and populate as many elements as possible in your templates using constant data from vocabularies
4)
Perhaps in a future edition the definition of the individual colors used will be made a configuration option
5)
this is because the RDBMS must be initialized, and the Entity Index re-created, each time RIMMF is started
6)
the typical example is a Work record containing multiple Related Work 'groups', each of which contained a Relationship Designator
7)
though there is still room for enhancement
8)
sorry, still learning about this update process
9)
dateOfExpressionExpressionExpression, copyrightDateManifestationManifestation, descriptionRelatedManifestationManifestation, dateOfWorkWorkWork, placeOfOriginOfTheWorkWorkWork, authorizedAccessPointRelatedExpressionExpression, authorizedAccessPointRelatedWorkWork, authorizedAccessPointWorkWork
10)
ie they have the same SubPropertyOf value
11)
because in our implementation of these relationship designators, there is an extra level between the Identifier and the Designator; we haven't changed the implementation, just the code for the OPAC view