It would be nice to limit what gets cataloged either by excluding or including. For example, if one is interested in cataloging the media files on a hard drive, cataloging all the system files, emails, etc., just bloats the catalog unnecessarily, and then slows searching and creates extraneous search results.
A command line export of the database to csv would allow this to be an automated function that could occur nightly.
Thanks for considering these.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know whether it's intended usage, but in "Catalog volume" dialog I used to set a folder name(e.g. "c:\mediafiles"), not a drive name, of my HDD to restrict catalogging process within.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The second paragraph is a separate idea. There are several command line options in the documentation, but exporting a csv is not included. I'd like to be able to cron or launchd this as a nightly task.
In case you're interesting in how your application is being used, here's a bit of what I'm doing. Our video department logs and backups footage, projects, documents, audio, and all the other assets associated to hard drives as near line storage (& archiving to LTO tape). I catalog the drives with VVV. Being able to use either a Mac or PC is great. I've cataloged 114 drives, and have a database around 500 MB. It really has been a great tool.
Additionally, what I am now doing is exporting a CSV which I then import into a MySQL database. I have a web search form tied to this which can be accessed anywhere, and which allows me to make queries easy for users (searching only for video files, for example). I can also use fulltext searches which makes queries on a database of this size exceedingly fast.
Thanks for providing the CSV export. It's something I really didn't find in other catalogs, so the database is always tied to the application. I understand and appreciate your reasons for using a firebird database - this is not a complaint from me - but I'm happy to find a way to export.
Thanks again for a wonderful tool, and for considering these options.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be nice to limit what gets cataloged either by excluding or including. For example, if one is interested in cataloging the media files on a hard drive, cataloging all the system files, emails, etc., just bloats the catalog unnecessarily, and then slows searching and creates extraneous search results.
A command line export of the database to csv would allow this to be an automated function that could occur nightly.
Thanks for considering these.
I did not understand the last paragraph: do you mean to be able to also filter the exported data?
I don't know whether it's intended usage, but in "Catalog volume" dialog I used to set a folder name(e.g. "c:\mediafiles"), not a drive name, of my HDD to restrict catalogging process within.
Sorry I didn't see your reply sooner.
The second paragraph is a separate idea. There are several command line options in the documentation, but exporting a csv is not included. I'd like to be able to cron or launchd this as a nightly task.
In case you're interesting in how your application is being used, here's a bit of what I'm doing. Our video department logs and backups footage, projects, documents, audio, and all the other assets associated to hard drives as near line storage (& archiving to LTO tape). I catalog the drives with VVV. Being able to use either a Mac or PC is great. I've cataloged 114 drives, and have a database around 500 MB. It really has been a great tool.
Additionally, what I am now doing is exporting a CSV which I then import into a MySQL database. I have a web search form tied to this which can be accessed anywhere, and which allows me to make queries easy for users (searching only for video files, for example). I can also use fulltext searches which makes queries on a database of this size exceedingly fast.
Thanks for providing the CSV export. It's something I really didn't find in other catalogs, so the database is always tied to the application. I understand and appreciate your reasons for using a firebird database - this is not a complaint from me - but I'm happy to find a way to export.
Thanks again for a wonderful tool, and for considering these options.