MARC Report 2.48: Program changes
- A new set of cataloging checks has been added that will display a message if a name heading is missing a relationship (that is, a 100, 110, 700, or 710 without $e; and a 111 or 711 without $j). It is important to specify the relationship between an Agent and a Resource–this will make your data more useful, especially if that data is to function well in the world to come after MARC. However, we have made it possible for you to turn these checks off: goto the Options, and on the RDA page, in the Appendix I section, uncheck the option labeled Show reminder if missing relationships.
- The program now supports doubleclicking on URLs that appear in the 'Help' screens. There are not a lot of URLs yet, but this change will probably encourage us to add more.
- This version includes an option to turn off the color-coding used in the brief message panel. This might make the messages easier to read for some users. To activate it, right-click on any brief message and select the option labeled Turn off color-coding of brief messages. Its a sticky option, and will remain set until you change it again.
- Several options have been added to customize the way that diacritics are displayed when you press <F3>. In addition, the method for specifying a custom diacritics file has changed. For the current documentation on this topic, refer to the following page: Customizing the Diacritics in MARC Report
- A number of cataloging checks for authority records, from an RDA point of view, have been enabled (these were provisionally added in the last version, but disabled). If you have customized your cat checks, you will need to enable these manually. For a list of the (nine) cat checks referred to here, go to the Cataloging check changes page for version 2.48
- Another new set of cataloging checks has been added that categorizes RDA relationship labels that have changed, have been deprecated, or are simply inappropriate in MARC. The details are here.
- The Help file for the MARC Split utility has been completely rewritten. This is to coincide with the new Split By Data option added in version 248.
- A new option has been added to MARC Review and MARC Global that tells the program to automatically remember the last 20 reviews created (whether you save them or not). The details are here.
- A number of changes have been made to the MARC Analysis utility. Some changes improve how the options are saved, and others add a new capability to the 'Custom lists' feature. The details are here. In addition, the consistency of the formatting of the various MARC Analysis report sections has been improved, and more helpful labels have been added to some sections.
- A new option has been added to MARC Review/MARC Global to automatically generate a unique filename for textfile output (applies to MARC Review text reports, and MARC Global change logs). So, for example, instead of every MARC Review run defaulting to a report named 'mreview.txt', they will now be named 'mreview.txt(1)', 'mreview.txt(2)', and so on, automatically. This option does not apply to MARC output, and it is turned off by default. To enable it, start the utility, click the Options button, and check the option at the bottom of the form.
- A minor change has been made to the results summary that appears after MARC Global has run. When a job resulted in no hits, the summary would not always list the desired action1). This made the corresponding entry in the History log less than useful. Now, the Global change options will always be displayed, regardless of whether there were hits or not.
- A new option named Edit Groups was added to the 'Saved reviews' form used by MARC Review and MARC Global. This option, when checked, enables the editing of multiple 'Review Group' cells simultaneously (as described in the Help for this form). After editing multiple 'Review Group' cells, uncheck this option to restore the default Windows highlighting used to select and edit cells.
- This version adds support for using diacritics in MARC Review and MARC Global patterns created from files of strings, aka 'list search'. To be recognized by the program, the diacritics should be entered using the backslash hex notation (eg. \xC2). The encoding used in such diacritics should match the character encoding of the records being searched.
for example, this would be the case in a 'Change Data' review that had no hits and did not specify a pre-processing pattern