'Rolling' (incremental) archive.

[rafiki]

I have read what has been said about incremental burning re: security etc. but I do think there is a strong case for some form of incremental archiving. I have many folders for specific topics -'Holiday 2002', 'Daughter's Graduation' etc which will not have any more pictures added. However, there are some folders to which I constantly add pictures - 'Home and Family', 'Photo Course Work' etc.

It would be very useful for me to be able to do an incremental archive to regularly update the new additions to folders by comparing the current scan to the last database and just adding the new files.

[MichaelT]

Could you explain a little more about what you mean.

Do you want to archive a new set that is only comprised of the pictures added to "Holiday2002" since the last Archive?

..or something different?

If you could give me some more details, please, I would understand your request..

Thanks..

[rafiki]

I just want to add new photos to the archive as I add them to the folders on the HD. Equivalent of an incremental backup.

[MichaelT]

Because the index would have to be redone for each incremental backup, and because we do not believe in the concept of having a disk that is not closed as an Archive, we will probably NOT choose to do this.

I would recommend the following concept that is more secure.

Let's say that you want to Archive the Holiday2002 folder each month as you add pictures to it. Burn an Archive set each month. The next month burn the entire folder (or folders again) and so forth.

The downside is a little more time, and a few disks to throw away. The upside is that you will have multiple copies of the archive as time goes on, and the Cds are secure because they are closed disks.

It is possible that we might modify our thinking down the road, but I feel very strongly that I want AC to close the disc after each session, otherwise you do not have a secure archive...and a multi-session disk is not as compatable as a single session disk so in the end the Archove would be compromised as well.

So we will use the more secure method, at least for now.

Does this make sense to you?



If you have some ideas that can fit into our paradigm, please let me know..

[rafiki]

Thanks for explaining your strategy. However, I feel that it won't serve well the many people who have folders that 'evolve' with time. Perhaps there could be an option to incrementally archive in the manner I suggest (maybe warning of the potential insecurity). Perhaps keeping the database on the HD would facilitate in the administration of this facility? Or even keeping a separate 'master disk' CD updated each time with the new database?

[MichaelT]

We are open to various strategies, and the options will evolve over time. What I have descibed is what we have planned for the short term.

Part or this pre-Release process is to gather input, but of course we cannot promise yes to everything at one time. So I think many things are possible and we will impliment as much as we can to keep as wide a customer base as possible. It is just a matter of time. As long as the user base supports the program we plan to meet their needs as best as possible.

Like all good programs it will mature like a fine wine. We are committed to doing this, but we have a lot to do in this early period. So we look forward to you growing with us if you can.

Thanks for the feedback. It is all taken very seriously. We have already implimented a few features that have been suggested during the pre-release period, this week, and will begin test tomorrow.

[rafiki]

Thaks Michael.