|
You could do that, but why bother? The method I outlined doesn't care about physical structure except when titles are added and it must record their paths which must be done in the dBASE already. If you wish to browse a "Shelf" set the dropdown lists to create the virtual shelf sorted by whatever criteria you like and voila. Think about how much this can speed up varying waits we experience now. All new titles can be dropped into one folder location and only that location need be checked each time you power cycle as deletions would go through the database as well. The ereader would only need to check for new books in that one location and not have to verify the database on every power cycle. It would move the new submission out of that directory and add it wherever it thought appropriate, or could even be set to preserve your directory/file structures. The actual physical locations are irrelevant, the file structure you see now is merely an abstract illusion represented to you by the file system.
|