Duplicate Label Reports using Texxmlreplicate

1. Duplicate Label Reports using Texxmlreplicate Beth L. Gamble Senior Systems Analyst Smithsonian – NMNH gambleb@si.edu NA EMu Users Group Meeting October 22, 2008

2. The Problem • Multiple labels based on a numeric field in the record itself. • Crystal had some solutions but there were maximum number of repeats allowed and it was VERY complicated. • Looked at the problem from the data perspective.

3. The Problem • The solution in the data was very simple. Duplicate the row of data as many times as you need duplicates. • Doing this manually for every report was out of the question. • We called in the superheroes. Ohhhhhh KE please help!

4. The Solution • KE wrote a script called Texxmlreplicate which located the field to be used for the number of repeats and would create the repeats in the XML prior to it being converted to CSV and sent to the user’s machine. • KE of course wrote this in such a way that it could be easily customized for different report needs and is available with a texpress upgrade to all customers.

5. emu-botlive@kellogg[25] pwd /emu/texpress/texapi/bin emu-botlive@kellogg[26] ls CVS/ texxmlctl* standaloneimport* texxmlexport* texcsvexport* texxmlodbc* texhtmlctl* texxmlreplicate* texhtmlserver* texxmlreplicate.old* texps* texxmlserver* texqlclient* texxmlslidewrapper* texxmladjust* texxmlslidewrapper.old2* texxmlbotlabelwrapper* xmlwf* emu-botlive@kellogg[27] more texxmlbotlabelwrapper #!/bin/sh texxmlreplicate -TOtherCounts -cCatOtherCountsValue –tCatOtherCounts Type="Duplicates Collected" <$1 >texxmlwrappertemp texxmlodbc texxmlwrappertemp rm texxmlwrappertemp emu-botlive@kellogg[28] Green is what KE provides.Red is what customer has to create. Must notify KE about any wrapper scripts you create so they can check them into the source repository for future upgrades to your version of EMu.

6. Catalog module Tab view of Other Counts Kind and Value used to determine duplication.

7. Create a System Registry entry giving a name to your wrapper script.

8. Create a System Registry setting for the default file extension. This report is still a Crystal Report so .rpt is used.

9. Create a System Registry entry telling EMu what format the final output should be in. This is an ODBC / CSV type of report just like other Crystal Reports.

10. Tell EMu what to do when this report is invoked. Again this is still just a Crystal report so you have to run the Crystal viewer with the report name parameter.

11. Finally you have to give this report type a name that will appear to the users in the Report Type box.

12. How a user selects this new type of Report. Notice this is the name you gave it in the Registry.

13. When selecting the fields for the report. Put the fields that will be used by the wrapper script to determine the duplication in their own group. This makes like much simpler, TRUST ME! Also, rename the group to something meaningful. GroupX is not recommended.

14. Within Crystal this is how the duplicated table is linked in the main report. By having the OtherCou_csv linked in the main report you get the necessary duplication. This is the Group you created in EMu with name slightly truncated. In this case the name was OtherCounts.

15. Within Crystal this is how the report is limited to only “Duplicates Collected”Other Counts for the Catalog Record. This is done via the Select Expert.

16. THE FINAL REPORT

17. KE comes through again! • Ask and you shall receive! • The steps associated with writing the wrapper script and defining the registry setting is done by your system administrator or KE. • The use of the report type and setting up the report in EMu can be done by the users. • Creating the report definition could be done by users or your institution’s Crystal Reports goto person.

18. Thanks  • May seem like many steps but it really is rather straight forward once you do it a time or two. • I am happy to help get you started so email me if any of this isn’t Crystal clear. • Beth L. Gamble – gambleb@si.edu