https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20678
--- Comment #7 from Alex Buckley <[email protected]> --- Created attachment 74960 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=74960&action=edit Bug 20678 - Added new Draft records interface in cataloging Instead of using the Tools->Manage Staged MARC records interface to list all draft records and links to edit or delete them I have created a new interface in the Cataloging module (draftrecords.pl) which is accessible by clicking the 'View draft records' button at the top of the Cataloging home page. draftrecords.pl contains a JS datatable of all draft records in the reservoir. There is a link to delete all draft records, in addition to individual 'Edit' and 'Delete' buttons for each draft record. This datatable is based on the datatable on the Manage Staged MARC records interface and I have removed unneccessary columns such as comments, type, staged timestamp etc. The rationale for creating a new Draft records interface in cataloging rather than using the existing Manage Staged MARC records interface is that it is more intuitive for librarians to look in cataloging for draft records to continue cataloging. They would be very unlikely to think draft records can be accessed from the Manage Staged MARC records. i.e. Although the draft records use the same backend infrastructure as the staged records the end-users don't know or care about that. Thus it is best to place the Draft records interface in the Cataloging module as the draft records are part way through the cataloging workflow. Also added to the Cataloging home page I have implemented a 'Drafts only' search parameter checkbox hidden by default, so if librarians know the title of the draft record they want they can find it quickly without wading through catalog records also matching the search term. Test plan: 1. Go to Tools->Manage Staged MARC records, notice the first batch file is not shown. This is the batch file associated with the draft records. This is hidden because this file is only needed due to foreign key constraints in the database but it is not needed to be imported and so it is safest to hide it. 2. Go to Cataloging and notice there is a new button in the cataloging toolbar named 'View draft records' 3. Create a new record and after inputting record data select Save->Save without cataloging. You have created a draft record. 4. Your re-directed to the Cataloging home page. Search for the draft record by writing in the search term and selecting 'Submit' and notice it is returned in the 'Biblios in the reservoir' search results. There may also be similarly named catalog records displayed in the result table above. 5. Now to limit the cataloging search to draft records select the [+] link next to the search box and select the 'Drafts only' checkbox. 6. Now notice that only draft records in the reservoir are returned. 7. Go and create another 3 draft records and then after you are re-directed to the Cataloging homepage click on the 'View draft records' button in the cataloging toolbar. 8. The 'View draft records' webpage is displayed. Notice all 4 draft records are displayed in the datatable. 9. Select the 'Edit' link of one of the draft records and notice the addbiblio.pl page for that record is displayed. 10. Commit the draft record to the catalog by selecting any option of the 'Save' dropdown box except for the 'Save without cataloging' option. 11. Then return to the 'View draft records' page and notice the committed record is not displayed as a draft in the reservoir. This can be confirmed by performing a Cataloging search which shows the record is in the catalog and has been removed from the reservoir. 12. Back in the 'View draft records' select the 'Delete' link beside one of the draft records, notice it is successfully deleted. 13. Select the 'Delete all drafts from reservoir' and notice all the drafts are removed successfully. NOTE: this patch has not added/amended routines in modules and so this patch does not require further unit tests to be added. I have previously added a unit test to address module routine changes made in previous patches on this bug. Sponsored-By: Toi Ohomai Institute of Technology -- 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/
