Question regarding form design and unordered lists in database

[mdkelly_komex]

Hi all,

I am just beginning to design a web application for online job postings for the company I work for and am having a bit of trouble getting over one point, unordered lists and their storage in a database.

Okay, I know I can just store the lists as a large block of text in the database, but I am hoping to get something a bit more elegant.

A bit of background. I will be creating on online-form so that certain employees can create and submit job postings for display on our website. The form will be pretty basic and allow entry of certian types of information with the main block of information being in the form of a couple of paragraphs and unordered lists, possibly and likely nested.

Once the form is submitted its data will be stored in a databased where it will then be extracted for display on a web page.

My stumbling blocks are coming with how to design the form such that the user can enter in items in the form of an unordered list. If it was only to be one one-level list that would not be so bad. It will possibly and likely be a list(s) with a few nested levels.

I want to design the form so that it is the easiest for the user to use, most people using it will have little computer experience, but yet is robust enough to allow them to do anything they would like, within the known constraints of the rules for creating a job posting.

Then it comes down to the database. Is there a more graceful way of storing lists such as above without just shoving all the info into a large text cell? Seems it would be a bit more challenging to do any rendering of the list if it was stored like that.

I know these may seem very general, and possibly simple questions, but for whatever reason I cannot wrap my head around it.

I have researched the use of a WYSIWYG editor as part of the web page that contains the form but I think it would be a little to big for what I am trying to accomplish, and also opens us the issues of browser dependancy.

Hoping to get some thoughts on the above from some of those more experienced with this than myself.

Thank you for your time

[Roger_Ramjet]

Job listings eh! I guess job description will be a block of text, just give them a textarea where they can paste it from Word or whatever. The unordered lists will be the required and prefered skills, qualifications and experience.

Well, unordered lists can be exploded into an array, which can be sorted and stored as you like. If it is nested lists then you could end up with an array of arrays, good luck with that.
Fulltext search will allow you to provide a search facility for the job descriptions.

Look, it is all very well to make it as unstructured as possible, but you can go too far with that idea. When it comes to data entry forms - keep it clean. White background, no animations, no visual noise. Give clear, concise instructions, indicate required fields clearly, and impose a logical order - users thrive on order.

Best way to develop a data entry form is rapid prototyping, you knock one up and pilot test it on significant users. You incorporate the changes required through a series of prototypes and tests untill the design emerges. The final prototype is then reverse engineered for processing efficiency.
Sounds like a lot doesn't it? All it really means is include the users in the design process. As the programmer, we are generally to close to the problem and our solution to put ourself into the users' shoes. What seems obviouse and easy to you can baffle a user, while the way they want it to work will sometimes baffle you.

[mdkelly_komex]

Thank you for the reply.

I had thought along similar lines for the unordered list and that allowing nested lists would definately complicate things.

I know where you are coming from when you talk about programmers being to close to the project to look at it from the user's perspective.

I will keep all your points in mind as I develop the solution

Thanks again