Unclear Requirement from client ... Ring a bell?

[galford23]

Hi all,

I am new to Java, but was ask to do a project from a client.

The deliverable is to produce an document archiving system running on Java + tomcat + Lucene

there is this requirement Which totally does not ring a bell... wondering anyone out that understand this statement.

"A user of the system will be able to create a document archive on a machine running a Tomcat (or Jetty) web-server.A document may come from an RSS feed (its content will be saved on the server along with data characterizing the original feed details)."

Really need help ... Try reading on the net for RSS , but how can I archive a RSS feed ?

[jelly]

RSS feeds are XML based so you could simply save the XML document from the feed

[galford23]

Meaning to say that if a user click on the XML Document where it bring the user to ?

[roots]

You should talk to client. More you talk with them more you talk more you will know how he wants the bell to ring.
Keep the local copy of the RSS Feed perhaps on lucene index itself. Pull the document from net using general java networking library or apache http components. Extract the XML data to different field like title, body and so on. Prepare lucene document out of that feed and store that in index.

Asking wont harm, talk to the client once more is this what you wanted by this.

[galford23]

Hi roots,

I have check up on the java networking library and understand file can be download, however it is this statement "its content will be saved on the server along with data characterizing the original feed details" that I do not quite get it.

Another requirement is "the archive will contain only a URL for a document that exists on the Web". no idea how to design this part of the project..
If it is a physical document (doc, pdf...etc)I understand that it can be uploaded manually via upload function -> go through lucene Index -> database storage.
URL ?

They leave it to us to design and we will present the 1st proposal in a couple of week time.

Maybe someone can help me to provide some link where I can research my self..

[roots]

Quote:

Originally Posted by galford23

its content will be saved on the server along with data characterizing the original feed details

In simplest term let's begin with an example RSS feed with attached content such as image. Now we can interpret the statement as image shall be saved on server along with the data (such as url, date, title .. ) if the original RSS feed.

I could not get this

Quote:

If it is a physical document (doc, pdf...etc)I understand that it can be uploaded manually via upload function -> go through lucene Index -> database storage.
URL ?

Quote:

Originally Posted by galford23

the archive will contain only a URL for a document that exists on the Web

I can guess your feeds will come with documents linked or attached to feed. In a case the document is linked to an URI then you only need to save that link in the database.

Review all the specification of RSS and other Feed types and talk to them. If they are not available then it's the client's fault.

[galford23]

Quote:

Originally Posted by roots

In simplest term let's begin with an example RSS feed with attached content such as image. Now we can interpret the statement as image shall be saved on server along with the data (such as url, date, title .. ) if the original RSS feed.

From my newbie understanding, I guess the only the XML file will go throught the indexing.
Meaning to say that will the image file that the feed point to, be saved as well? If yes how can it be achieve?

[roots]

That's the good point. Except for text content nothing can be stored in Lucene. Things like Image should be either saved in file system or the database. With just lucene and File System solution you can store non text document in a file system and include their path information in lucene.

.. not ringing bell is again the problem here .. what are the possible document formats .. Is it just text in the feed and the text contained in content pointed by feed or something as well... In real sense we talking out of our assumption will increase the scope of application but doesnot necessarily address what customer wants.. once again you should talk to client ..