[Koha-bugs] [Bug 8956] New: Split serials enumeration data into separate fields

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Oct 23 15:49:02 CEST 2012


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8956

          Priority: P5 - low
 Change sponsored?: ---
            Bug ID: 8956
                CC: colin.campbell at ptfs-europe.com
          Assignee: koha-bugs at lists.koha-community.org
           Summary: Split serials enumeration data into separate fields
          Severity: enhancement
    Classification: Unclassified
                OS: All
          Reporter: kyle at bywatersolutions.com
          Hardware: All
            Status: NEW
           Version: master
         Component: Serials
           Product: Koha

Work to be done

1)   Add an option 'published_end_date' to the serials table. It will only be
used to represent the last issue date in a bound volume.
2)   Data clean up:  Extract the published dates from the existing enumeration
field. Populate serials.publisheddate and serials.published_end_date with this
data.
3)   Strip the publishing dates from their enumeration fields (probably by
simply deleting matched parentheses and everything in between them).
4)   In order to break the “Numbered” field into three columns, add X, Y and Z
columns to serials, as well as X, Y and Z descriptions columns to the
subscription table.
5)   Port existing data into these columns.  Once all the enumeration fields
are of the correct format, e.g., Vol. X No. Y, we can use everything preceding
{X} as X_Description, and everything preceding {Y} until } as Y_Description. 
Another way to look at this is if we split on {?}, we will have all the label
fields in order of use. Once we have the label fields, we can parse those out
of the enumeration string, and we will have the set of values they represent.
6)   Add a calendar widget for published on and expected on (serials-edit.pl).
This will require librarians to enter new dates in the accepted format.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list