Questions from a Newbie

Submitted by Yuri on Mon, 08/08/2011 - 17:04

Implementation discussion

I've now got OV installed and am starting to climb the rather steep learning curve. Using a combination of posts from this forum, I've put together a setup tutorial for installation on a 32- or 64-bit Windows 7 PCs. I welcome any constructive criticism: browse to http://www.openvpms.org/documentation/installing-openvpms-windows-7-comp....

First question: is there any way to turn off "propercasing" globally? I ask as I'm running into a few challenges with this OV function:

1. Full-stops are an issue: type in "1.8kg" in inventory names and oV changes it to "1. 8kg". No amount of re-editing will let "1.8kg" stick; I now use "1,8kg" and oV doesn't throw in the extra space.

2. It's a two-step process to add anything that's a title or acronym: ie type in FIV, oV changes that to Fiv, you re-edit it to FIV, click Ok and FIV sticks. Other acronyms/titles like Bvsc/BVSc also need the two-step edit.

3. I note that whilst the postcodes.xml file has all of Australia's placenames in capitals, they are all changed to proper case once they appear in OV, even though Australia Post's guidelines state that placename and state are supposed to be all capitalised for mailing.

Second question: is there any way to print a current customer label (ie to stick on an envelope or to label a collar or blanket left behind).

EDITED: 19 July 2012 to correct URL pointing to installation tutorial.

Re: Questions from a Newbie

Submitted by tanderson on Wed, 10/08/2011 - 15:30.

There is no direct facility to disable propercasing globally. You can disable it for specific archetype nodes by removing the <assertion name="propercase"/>
e.g. for the name node of product.medication:
    <archetype name="product.medication.1.0" latest="true"
               type="org.openvpms.component.business.domain.im.product.Product" displayName="Medication">
        <node name="id" path="/id"
              type="java.lang.Long" readOnly="true"/>
        <node name="name" path="/name" type="java.lang.String" minCardinality="1">
            <assertion name="propercase"/> 
        </node>

You can customise propercasing by editing $TOMCAT_HOME/webapps/openvpms/WEB-INF/classes/org/openvpms/web/resource/localisation/propercase.properties

You'll need to restart the webapp to see changes.

Taking your other points in turn:

1. You can fix this by removing:
spaceAfter.2 = .
in propercase.properties.

2. You can fix this by adding:

exceptions.10 = FIV
exceptions.11 = BVSc

to propercase.properties.

3. The lookup.state code probably should be used in addresses, but it looks like the lookup.state name is being used instead. Ideally, the code node would represent the ISO state code, but I understand its difficult to enforce this when migrating from other systems.
Wasn't aware of the placename guideline - in any case, the source data is all mixed case, its the unique codes in uppercase.

4. There's no direct way of printing a current customer label, although you can do it by creating a report which takes the customer name or id as a parameter. You'd run this report from the Reporting -> Report workspace.

I've had a quick look at your documentation - looks good. When you add it to the documentation, it would be good in book form, with one page per topic.

Regards,

Tim

Re: Questions from a Newbie

Submitted by Yuri on Fri, 12/08/2011 - 12:12.

Tim said

>Printing a current customer label, although you can do it by creating a report which takes the customer name or id as a parameter. You'd run this report from the Reporting -> Report workspace.

Hi Tim

To see how it's done, I downloaded Matt's "Patient Admission Label (7.2cm x 5.4cm)" label from the shared resource's page. I clicked Admin | Templates | New, added it as a new report (browse | send). I then picked a customer, picked their patient then went to Reporting | Reports, selected that report and clicked Run. I received an error message "Unsupported Document Template: Form Label Admission Ver 2.odt".

Reading the website again, I noted that the description for the label says ver 1.3 or earlier (I'm using v1.4), so I then downloaded Tony's Postcard Reminder (dated 18/05/11), repeated the above procedure and still got the Unsupported Document Template error.

What have I done wrong now?

Yuri.

Re: Questions from a Newbie

Submitted by tanderson on Fri, 12/08/2011 - 13:38.

It needs to be a Jasper Report that has an SQL query. I don't think there is any at the moment that do what you want to do, but you could adapt one, like the Customer Acquisition Report which is included in the distribution.

-Tim

Re: Questions from a Newbie

Submitted by tanderson on Fri, 12/08/2011 - 13:56.

Actually, another way to do it would be to create a Customer Form template.

You would create a new document in the Customer -> Documents workspace using the form, for the customer you want a label for and then print it. Once printed, you can delete the document. Not ideal, but may be simpler than the reporting approach.

See the Desexing Certificate for an example, in Administration -> Templates.

-Tim

Re: Questions from a Newbie

Submitted by Yuri on Fri, 12/08/2011 - 15:58.

EUREKA!

That's it! Perfect. The penny has dropped: Matt's Admission Label is a "Patient Form", not a "Report". As soon as I changed the type, I could select it in Patients | Documents and print it out. Now a simple (?) matter to rename and reformat a desexing certificate with the bits I need suitable for a Seiko label printer.

Thanks, Tim, much appreciated.

Yuri.