http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11023
Laurence Lefaucheur <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |laurence.lefaucheur@biblibr | |e.com --- Comment #36 from Laurence Lefaucheur <[email protected]> --- Just some more information on how the dev works before answering more in details to Katrin's notes The goal of the cronjob is to remove a "new" information from items after a given period. What could be a "new" information in the item : 1) a 'new' status added just to inform about the new document : we suppose an item subfield mapped with items.new field. This value can be used in search (if zebra index is configured), for custom rss feeds ; the subfield can be linked to an authorised value (authorised value=1, label=New). The cronjob will delete the value in the 'new' subfield. 2) a 'New' itype (itemtype) so that specific issuing rules can be defined for new items. With this configuration, final itemtype can be defined based on condition in another item subfield (ccode) or in a biblio subfield (mapped with biblioitems.itemtype) or in any items or biblioitems available field. The cronjob will delete the 'New' itype value and replace it by the suitable itype) 3) why not both of 1) and 2) or any item subfield the library wants to have some 'new' information. Only items are modified, the modification of biblio (biblio or biblioitems) is not part of the dev. Biblioitems fields are used only for the condition criteria. The items having dateaccessioned <= Now-duration will be modified by the job. -- 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/
