NOTE: The following query commands DO NOT depend on the underlying catalog implementation. The names SQL and Lucene instead describe the query SYNTAX not the File Manager catalog. This means you can execute the sqlquery command against a File Manager with a Lucene index, and vice versa.
This will execute a Lucene Query against the filemanager catalog and return a list of ProductIDs. These Product IDs can then be piped into the fmdel alias to remove all products that match the query criteria.
Usage:
lucenequery "ProductType:ISMRawData"
|
lucenequery "ProductType:ISMRawData" > ProductID_List.txt
|
This will execute as SQL Query against the filemanager catalog and return the metadata value(s) specified in the SELECT statement. You can also declare more than one ProductType in the FROM statement. This enables you to create metadata exports into a csv file format using this tool. In the second usage example you can chain together any number of available metadata keys to pull out the corresponding values.
Usage:
sqlquery "SELECT CAS.ProductId FROM GenericFile"
|
sqlquery "SELECT CAS.ProductId,CAS.ProductName,CAS.ProductReceivedTime FROM GenericFile" > CAS_Metadata.csv
|
sqlquery "SELECT CAS.ProductId FROM GenericFile,ProductType2,ProductType3,ProductTypeN"
|
Use this command to delete a single product from the catalog. This will remove the lucene index entry from the catalog and will remove the archived product from disk. (If you just want to SEE/PREVIEW what products will be removed from the archive, then you will need to use the --nocommit parameter)
Usage:
fmdel --nocommit 0691ee17-96ec-11e0-8556-3b3ca12e4f64
|
fmdel 0691ee17-96ec-11e0-8556-3b3ca12e4f64
|
Just added to the list. This will take in a product_id and dump out the product's metadata into the current directory. This one needs a little more testing and docs.
Usage:
lucenequery "ProductType:GenericFile" | fmdel
|