Here are a couple of related rough edges in the Categories module for which improvements in a patch would be good.
Background: I have one category tree that contains definitions (mostly for looking up abbreviations) and another that I use for tagging records. In the "definitions tree" I already have a category for the abbreviation NPP.
One Problem: I created an NPP category in my "tagging tree," using the right-hand panel from the opened record. Biblioscape let me do this with no error message. I then put a check mark there. I'm not sure when, but then or shortly afterward I got a belated "duplicate name" error for the new NPP category, so I selected the the option of giving it a new name, calling it "NPP-". However, in the bottom of the right-hand pane the record was tagged as "NPP", not "NPP-".
There Are Actually Four Problems Here, I Think: (1) The error message should be immediate, when the creation of duplicate is attempted; (2) the location (i.e. full path) of the original same-named item should be disclosed in the error message; (3) the creation of a duplicate should (at least as the default option) be disallowed; and (4) updating of the display of a record's categorizations (bottom of the right-hand pane) should be immediate and accurate.
Also, consideration should be given to fixes (1) through (3) in other modules, for when a user tries make a duplicate item (i.e. two references of the same name, two notes of the same name, etc.).
Larry, I cannot reproduce
Larry, I cannot reproduce this. When a new category is added with the same name as an existing one, Biblioscape does prompt the user. Can you reproduce this? You can zip all the files under your database folder and email me the zip. I will try to reproduce it.
.
Hi Paul,
The problem is repeatable, so I give more detailed instructions for its replication:
1. I have a main category folder, and a child folder under it for acronym definitions. Open the Definitions folder and create a new category named NNN, and put "test" in the description. Save and close.
2. Exit Biblioscape. (May not be necessary, but makes test more robust.) Reload Biblioscape.
3. Create a new reference. With the reference open, in the right hand pane, open the main categories folder (not the Definitions one). Select a category there (I chose "Models"), and create a child folder under it, naming it NNN. [Note: There is no error message yet about a duplicate category name.]
4. Activate the checkbox for NNN. NNN appears in the record's category listing at the bottom of the righthand pane. [Note: there is still no error message about a duplicate name.]
5. Click Save & Close for the record. This error message appears: "The category name NNN has been used already. Do you want to use another?"
6. Click "Yes" and rename the category as "NNN-".
7. At this point the reference is closed, so reopen it.
8. Note that the in the record's main pane the Categories field contains "Models" and "NNN". If you click NNN what gets opened is the NNN category in the Definitions folder, and you can see the "Test" description there.
9. Return to the opened reference record. Click the Categories tab in the right hand pane, and look under Models. The child category is correctly "NNN-". However, the problem is that the category assigned to the reference was the wrong name in the wrong Category folder.
SUMMARY: There are two problems here. (1) The duplicate name error message is appearing too late. It should appear when the user first attempts to use a duplicate of the preexisting name. (2) Even after the user selects a revised name for the new category, the incorrrect preexisting name (and actual category) is inserted into the reference record.
Also: (3) The error message is frustrating because it does not tell the user where the preexisting category is located (i.e. the path to it). I have a complex set of categories, and this is like a needle in a haystack. To deal with the error and do whatever renaming makes sense (of either the new or old category, or both), I need to find the original. (4) The error message should have an added choice of "Cancel," in addition to Yes and No. Of course, however, this would work only if the error message appears when it should; before the category is actually created.
Yes, I can now reproduce it.
Yes, I can now reproduce it. The problem can be solved by checking the duplicate earlier. The fix will be in the next patch release. Thank you for your detailed description. Paul
.
Thanks, Paul!