Hi,
I am developing a HR type application and need some help trying to decide
what is best for the following situation.
I need to allow users to enter resume data in a web page. Once they have
entered all the data I would like to save it to a SQL Server database.
Here's the trick. I need to be able to retrieve the data from the database
and then manipulate it and allow the user to choose different resume styles
they would like to see the data displayed in. I also need to be able to
accept and provide (from or to an external source) this resume data in a
format that conforms to the HR-XML (www.hr-xml.org) standard.
So I figured I would build an interface that could take an xml file that is
HR-XML compliant and save the data to the database or vice versa. Then when
the user enters the data for their resume this data would be compiled into an
HR-XML compliant XML file and fed through the interface. If I was accepting
a file from an external source then that file would also be fed through the
same interface.
Does this make sense? I'm not new to XML, but I really haven't done much in
it yet, so I'm not sure if this is the best approach or not. Please feel
free to ask any questions you might need for clarification.
Thanks,
Wes
Hello, Wes!
You wrote on Tue, 19 Oct 2004 07:41:11 -0700:
W> I am developing a HR type application and need some help trying to
W> decide what is best for the following situation.
W> I need to allow users to enter resume data in a web page. Once they
W> have entered all the data I would like to save it to a SQL Server
W> database. Here's the trick. I need to be able to retrieve the data
W> from the database and then manipulate it and allow the user to choose
W> different resume styles they would like to see the data displayed in. I
W> also need to be able to accept and provide (from or to an external
W> source) this resume data in a format that conforms to the HR-XML
W> (www.hr-xml.org) standard.
You can produce xml document in the following manner
a) load all data from server to local recordset or dataset (ado.net) and
create xml manually, for example via XmlWriter
b) write complex and nontrivial "for xml explicit" query. In that case xml
document will be generated on the server without your intervention.
When you get xml document you will be able to apply different styles for
resume using xslt and css.
W> So I figured I would build an interface that could take an xml file that
W> is HR-XML compliant and save the data to the database or vice versa.
You can use annotated xml schema (AXD) to automaticaly map xml document to
relational schema.
W> Then when the user enters the data for their resume this data would be
W> compiled into an HR-XML compliant XML file and fed through the
W> interface.
It is good architectural decision to provide one way for incoming data to be
in database.
W> If I was accepting a file from an external source then that file would
W> also be fed through the same interface.
W> Does this make sense? I'm not new to XML, but I really haven't done
W> much in it yet, so I'm not sure if this is the best approach or not.
W> Please feel free to ask any questions you might need for clarification.
W> Thanks,
With best regards, Alex Shirshov.
Friday, March 23, 2012
Saving and manipulating XML data
Labels:
application,
database,
decidewhat,
developing,
enter,
following,
manipulating,
microsoft,
mysql,
oracle,
saving,
server,
situation,
sql,
type,
users,
xml
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment