[Koha-bugs] [Bug 5062] New: Acq terminology: list price, ordering price, vendor price, RRP

[bugzilla-daemon at bugs.koha-community.org]

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

           Summary: Acq terminology: list price, ordering price, vendor
                    price, RRP
 Change sponsored?: ---
           Product: Koha
           Version: rel_3_2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Templates
        AssignedTo: oleonard at myacpl.org
        ReportedBy: katrin.fischer at bsz-bw.de
         QAContact: koha-bugs at lists.koha-community.org
   Estimated Hours: 0.0


In acquisitions there are different terms used for the same thing in the
database.

The vendor form uses 'ordering price' and 'list price', the new order form uses
'vendor price'.

I wrote a patch to change 'ordering price' to 'list price' in the new vendor
form, because this term was used in all other places in this template. (bug
5059)

Now I found 'vendor price' in the new order form.

The basket view uses 'RRP' (see screenshot)

The PDF print layout 'pdfformat::layout3pages' uses 'RRT GST Inc.' as column
heading.

Comments from discussion on IRC:
(15:21:47) slef: I'm looking at ODLIS
(15:23:41) slef: It says in "list price"'s definition "Synonymous with
published price and retail price" but I suspect this might be a subtle
difference between "list price" and "retail price"

(15:08:27) nengard: i think vendor price might be the safest option
(15:08:37) nengard: that says to me the price the vendor is charging
(15:08:48) nengard: or the price the vendor has listed on their site or in
their catalog

I'm not a native speaker, so not sure which term to choose. But I think
reducing the used terms to one would make things (translation, documentation,
trainign) a lot easier!

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.