Updated Spec -Build a routine to split out elements *.xml file to a *.dbf & *.csv
- or -
Post a project like this- Posted:
- Proposals: 8
- Remote
- #1252087
- Expired
Description
Overview- See Attached document
We produce membership cards on behalf of our client. Personalised cards are sent with personalised letters. Recipients receive from 1 to 4 cards attached to a single letter. There are two letter and card types. XML files are received and we are required to output a combination of DBF and CSV files.
Requirement Overview
1. Parse received XML file
2. Split and group data depending on card/letter type (Premium or Standard)
3. Transform XML to specific DBF schema and CSV format x 2 (1 x Premium and 1 x Standard)
Enda C.
100% (2)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Hello Enda,
Is this job still open?
RaluEnda C.06 Sep 2016yes job still open .. i will be putting up a revised specification shortly
Ralu P.06 Sep 2016Awesome.
-
Hi,
in the XML file PLATINIUM is in the "membershipType" element but in the CSV/DBF it's in the coverCode column, could confirm that's how it should be please?
Thank you,
Lucy -
Hi, Thanks for inviting me to bid on this. In order to be able to give you a more accurate quote on this could you please clarify what is you preferred language of the script/routine to be developed on? Also, are you aware that XMLs are tree like data structures and DBFs and CSVs are basically table (linear records) like data structures? Additionally, the CSV provided as examples doesn't seem to have the same records as the XML they were supposed to be created from., Cheers, Tom
Enda C.16 Aug 2016Hi Tom, Thanks for your reply and .. we are aware of the items below and one of my colleagues inadvertently include a slightly different *.xml file that had some additional entries within it ..
Thanks for the reply .. By way of background ..
We need to manage the receipt of data and the printing of membership cards and attaching them to a personalised letter and posting for our customer.
There are two types of cards ( Standard & Platinium) and a recipient can receive between 1 & 4 cards on a single personalised letter .
Our production process requires us to filter the data into a number of folders/ files .
1. Platinium Cards or Standard Cards
2. Members that will receive one card per letter , two cards per letter , three cards per letter , four cards per letter.
3. CSV data for our card personalisation process
4. *.dbf data for our letter printing and card matching process ( fields extracted from *.xml will be different from fields extracted for *csv but with one common field to both "membership number "
Once the (Standard or Platinium) cards have been over printed using the appropriate *.CSV file , a corresponding *. DBF file ( Standard or Platinium) are loaded into the database on our letter printing and card matching line with one primary field common to both CSV & DBF ( membership number ) The printed cards are then loaded into the machine along with the *.dbf and a camera reads the membership number from the card and prints the corresponding letter generated from the corresponding data within the *.dbf . Card is matched to the letter and automatically put in an envelope.
Where a recipient will receive multiple cards ( up to 4 ) on one letter there is a requirement to append and additional field to each entry in the *.dbf data and to segregate all 1's 2's 3's 4's into 4 separate databases or 8 if you factor in the two additional variable of Standard or Platinium
Hope this helps clarify ... let me know if you have any further questions ..
Enda
Tom C.18 Aug 2016Thanks for your elaborated answer. In the meantime, I did put up a proposal as well, but not quite sure if this is still on? Cheers, Tom