Document Archiving
-
I'm looking at implementing document storage and versioning for our ASP.NET application, and I would appreciate some input on various methods used, designs etc. Google seems to just yield adverts for document archiving systems, but I would like to investigate implementing our own as well.
-
I'm looking at implementing document storage and versioning for our ASP.NET application, and I would appreciate some input on various methods used, designs etc. Google seems to just yield adverts for document archiving systems, but I would like to investigate implementing our own as well.
Brady - effectively there are two mechanisms for achieving this. The first is to store the file in a database and use triggers to help you achieve versioning. The second is to store the file on a disk, and then store the path to the file (probably in a database). If you choose to store the path, you need to rename the file to something unique (e.g. a GUID), and map this back to the original filename in the database - fortunately this is incredibly easy to do. I'm unsure as to what you ultimately need to know, so if you want to refine your question or ask for more information, let me know.
Deja View - the feeling that you've seen this post before.
-
Brady - effectively there are two mechanisms for achieving this. The first is to store the file in a database and use triggers to help you achieve versioning. The second is to store the file on a disk, and then store the path to the file (probably in a database). If you choose to store the path, you need to rename the file to something unique (e.g. a GUID), and map this back to the original filename in the database - fortunately this is incredibly easy to do. I'm unsure as to what you ultimately need to know, so if you want to refine your question or ask for more information, let me know.
Deja View - the feeling that you've seen this post before.
Thanks Pete. We already use the stored path approach, but I've just met with my team lead, and the requirement wasn't described very well. All I need to do is move older documents 'off-site', i.e. remove them from the operational folder, on demand. The versioning actually refers to database based documents such as cost estimates, invoices etc.
-
Thanks Pete. We already use the stored path approach, but I've just met with my team lead, and the requirement wasn't described very well. All I need to do is move older documents 'off-site', i.e. remove them from the operational folder, on demand. The versioning actually refers to database based documents such as cost estimates, invoices etc.
Brady Kelly wrote:
the requirement wasn't described very well.
Isn't that always the case. Not only do the lunatics end up running the asylum, they get to decide who gets committed there as well.
Deja View - the feeling that you've seen this post before.
-
Brady Kelly wrote:
the requirement wasn't described very well.
Isn't that always the case. Not only do the lunatics end up running the asylum, they get to decide who gets committed there as well.
Deja View - the feeling that you've seen this post before.
I'm quite lucky. Nearly all issues are logged internally, and only require a ten minute, in office, chat to sort out. At least we don't work off specs for this, the paperwork would be enormous.