<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.6000.16481" name=GENERATOR></HEAD>
<BODY>
<DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma
size=2></FONT></DIV><FONT face=Arial size=2><SPAN class=296465415-15082007><FONT
color=#0000ff></FONT>Requirements:</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial><FONT size=2><SPAN class=296465415-15082007><SPAN
class=500181219-15082007><FONT color=#0000ff> Assumption:
</FONT></SPAN>Input file <SPAN class=500181219-15082007><FONT
color=#0000ff> = </FONT></SPAN></SPAN><SPAN
class=296465415-15082007>standard XML file {e.g <A
href="http://www.w3schools.com/xml/note.xml">http://www.w3schools.com/xml/note.xml</A>}</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>i) Enable user
input of custom XML page by provision of web address url to an XML page
</SPAN></FONT><FONT face=Arial size=2><SPAN class=296465415-15082007>(in
similar fashion to feed; but it is not a feed)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>
Possible enable user input via browser paste (thoughts for/against
welcome)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>ii) Primary parse
to display and allow 'deselection' of fields from XML import that are not
required (by default, or set default to 'select' required)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>iii) Import XML
(with additional parameters set in ii) to [custom] node
type</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>iii) Enable edit
of imported node list (such as deletion of non-required records from list -
can/may arguably be done with content listing by type)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>iv) Enable linking
of key# data field in XML import to key# data field in existing nodes (of
type) for duplicate identification and/or replacement [or default
global replace - achieved by relevant call to
drupal].</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>My findings
suggest that:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- there is nothing
currently available to import XML pages with custom data
sets</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- there are some
that require same</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- CCK and Views
may be suitable to help make this a generic contribution by way of creating
destination node type? Also 'know of node import' but not yet investigated
relevancy</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007> (question
to note - if use CCK do we have access to data [ie is it stored seperately?]
in DB for later export or additional requirments?)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- there are some
existing API's for RSS/XML but I'm not sure if anything of use for this
application</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- there is some
'Google SUmmer of Code' work to look at feeds; but I do not think
this is relevant.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>I have not
developed anything custom for Drupal for a couple of years and find the mix of
contribs in this area 'confusing' so please lend me your
wisdom:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- any suggested
approaches to re-use existing API's and contributions</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- any existing
projects underway that this might impact or work with</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>- any willing
developers / helpers /shadowers to help ramp up and/or to build a
module for this</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>Additional
Comments:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>This capability
would be great for commercial applications.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>If I do this it is
likely to be in the near future and to customer time constraints I would be
happy to contribute back to drupal.</SPAN></FONT><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>As you can see
this i not specd yet but these are my ideas so far based on my client
requirement and 'quick' initial look at available options</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=296465415-15082007>Any head start
with better approach, where to look, who to talk to and what to research
to measure viability/effort required would be very welcome
indeed.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007>regards</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=296465415-15082007>Chris.</SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>