http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11559
Christopher Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #115 from Christopher Davis <[email protected]> --- (In reply to Jesse Weaver from comment #73) > Notes: All settings, including switching between the basic editor and > Rancor, are saved per-user as local settings. This means they should be > completely separated by user (though not private). Also, the [@number] > markings are just an artifact of the software used to prepare this. > > The individual parts of this test plan should be separately testable; please > test what you can! > > 1. Apply patch. > > *** Part 1 - Navigating to editor > 2. [@2] Go to the Cataloging section. > 3. Click on "Advanced editor." This should take you to Rancor with an empty > record loaded. > 4. Click on "Settings" -> "Switch to basic editor," then "OK." This should > switch to the basic editor with an empty record. > 5. Click on "Switch to advanced editor." This should take you back to Rancor. > 6. Navigate to a record, and click "Edit" -> "Edit record." This should load > the record in Rancor. > 7. Verify that clicking on "(view)" and "(edit items)" go to the correct > screens for the current record (in a new window). > 8. Click "Settings" -> "Switch to basic editor," then repeat. This should > now load in the basic editor. Click "Switch to advanced editor" for the > following steps. > 9. Go back to the Cataloging home page. > 10. Click on "New from Z39.50/SRU," run a Z39.50 search (doesn't matter what > for) and click "Import." This should open in the basic editor; the old-style > Z39.50 search interface is separate from that built into Rancor. > *** Part 2 - Editing records > 11. [@11] Return back to a new record in Rancor. > 12. Verify that the data portion non-control fields (>010) can be freely > typed into. Typing a dollar sign, alphanumeric and a space should create a > new subfield. For known MARC subfields, the description of the current field > (and subfield) should be shown in the status bar at the bottom. > 13. The data portion of control fields, tag numbers and indicators should be > editable, but in overwrite mode. If a syntactically incorrect MARC tag is > entered, the entire line should lose any other highlighting and turn red. > 14. For known fixed fields (currently only MARC21 leader or 000, 005 and > 008), the data portion of the field should be displayed as a widget, with > underlined portions that expand into text fields/dropdowns for the various > coded parts of the field. These widgets are toggleable in the settings. > 15. Subfields with authorized values attached to them should also be > displayed as simple, single-dropdown widgets. > 16. It should be possible to tab between the tag number, indicators, each > subfield and each element in a fixed field widget. Typing values for these > fields should work as expected. > 17. By pressing Enter anywhere in a field, the cursor should be moved to a > new field on the next line. > 18. After typing in the number of a tag, pressing Tab should tab through and > automatically create the indicator positions. > 19. By pressing Ctrl-X, the entire field should be deleted. > > *** Part 3 - Record Import/Export > 20. [@20] By entering text into any of the given fields on the left, a > search will be run with the given search field and contents (and none of the > others). Verify that they can be focused with their listed keyboard > shortcuts. > 21. Click on the checkboxes next to any of the available search targets to > enable/disable that target. > 22. Click on the arrows above any column to resort the results by that > column. Sorting defaults to title. NOTE: performance of the above will be > severely degraded if Koha::Cache is not running in memcached/fastmmap mode. > 23. Click on "View MARC" to show a preview of the record contents, and "Hide > MARC" to return to the original view. > 24. Click on "Import", and the record contents should be replaced with that > of the selected record. > 25. Click on "Advanced" in the search box on the left. > 26. Check or uncheck any of the servers to enable/disable them before the > search. The search query will be ANDed together from any non-empty fields. > 27. Verify that advanced search behaves similarly to a quick search after > results are returned. > 28. Open an existing catalog record in Rancor. > 29. Perform a search, and verify that "Substitute" copies the record > contents into the current catalog record, while "Import" starts editing a > new record. > 30. Verify that "Save" correctly saves record contents to the catalog. > 31. Click on the dropdown next to "Save to catalog," then either "Save as > ISO2709 (.mrc) file" or "Save as MARCXML (.xml) file." Click "Save file" (or > your browser's equivalent), then verify that the exported record's contents > are correct. > 32. Click on "Import record", then any ISO-2709 (.mrc) or MARC-XML (.xml) > record. The record contents should be loaded. > > *** Part 4 - Settings/Macros > 33. [@33] The "Settings" menu contains several font configuration options. > Verify that they all work as expected (some fonts may not exist on your > system). > 34. Click on "Macros." This should bring up a screen with no existing macros. > 35. Click "New macro..." and type in a name for the new macro. It should be > added to the list on the side. > 36. The format dropdown exists to allow compatibility with a proprietary > vendor format; the default of Rancor should be sufficient. > 37. Type any text into the macro editor, and it should be autosaved after a > brief delay. > 38. Hit "Delete macro" to delete this macro. > 39. Create a new macro, insert some text, wait for it to autosave, then > reload the page to verify that the macro contents are saved. > 40. Enter in some test macros, and verify that they work as expected. There > are a number of possible macro commands, but all are variants of two basic > forms: > - delete TARGET :: Deletes the given TARGET. > - TARGET=SOURCE :: Copies the contents of SOURCE into TARGET (spaces > around the equals sign are not allowed for reasons of ambiguity in fixed > fields). > 41. The possible targets are (specific tags/subfields are used, but only as > examples): > - 001 :: The entire contents of a control field (will be created if > needed). > - 245 :: The entire contents of the first 245 field (will be created if > needed). > - new 245 :: The entire contents of a new 245 field, inserted in > numerical order. > - new 245 grouped :: The entire contents of a new 245 field, inserted at > the end of the 200s. > - 245a OR 245a at end :: The contents of the $a subfield of the first > 245 field (will be created at the end of the field if needed). > - 245a after c :: The contents of the 245 $a subfield (will be created > after the $c subfield if needed). > - new 245a OR new 245a at end OR new 245a after c :: The contents of a > new 245 $a subfield in the given position. > - $a :: The contents of the $a subfield of the last mentioned tag. > - 245 indicators OR indicators :: Sets both indicators of either the > first field with the given tag or the last mentioned tag. > 42. The possible sources are: > - 001 OR 245 :: The entire contents of the first field with the given > tag. > - 245a :: The contents of the first $a subfield of the first 245 field. > 43. Some example commands: > - new 245=$a Charlotte's Web /$c by E.B. White. > - delete 245c > - 003=ByWater > 44. Verify that entering a syntactically correct macro and hitting "Run > macro" closes the macro editor and runs the given macro. To Whom It May Concern: In the above test plan, step number fifteen (15) states, "Subfields with authorized values attached to them should also be displayed as simple, single-dropdown widgets." When I proceed through this test plan, I cannot find any single-dropdown widgets in the MARC record which I create, except for those in, for example, MARC field 008. Is the "authorized values" mentioned in step fifteen of the test plan referring to authorized headings/access points or is this term referring to Koha authorized values such as Koha CCODES, location codes, NOT_LOAN codes, etc.? Please help me understand so that I can proceed with signing off this bug. Thank you, Christopher Davis, MLS Systems & E-Services Librarian Uintah County Library -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
