Page History

...

By default, the Solr File Manager will assign a newly generated UUID as the product unique identifier.
As a consequence, if the FM client sends the same physical product twice, two distinct records will be created in the Solr index.

org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.UUIDProductIdGenerator

Another possibility is to configure the Solr File Manager to use the product name as the unique identifier. In this case, if the
same product is ingested for a second time, the new Solr document will completely override the previous one, resulting in only
one product record in the catalog.

...

...

org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.NameProductIdGenerator

Alternatively, a project can provide a custom algorithm to generate product identifiers (for example, based on the system time
when the product is ingested) by implementing the ProductIdGenerator interface.o Generation

Serialization/Deserialization of Solr documents from product metadata.

When a physical product is sent for archiving to the File Manager, the associated metadata must be transformed into query-able information
that information that is stored in the back-end Solr catalog. By default, the Solr File Manager will transform each product into one corresponding Solr
documentSolr document, thus generating a single searchable record in the Solr index. Each product attribute is transformed into a corresponding Solr
field Solr field with the same name and value(s) (note that all fields MUST must be defined in the project specific schema deployed with the Solr installation).

Alternatively, a project may provide its own algorithm for generating Solr records from a CAS product by implementing the ProductSerializer interface.
For  For example, a project that manages products composed of full directories may wish to create a "collection"-level Solr record for the enclosing directory,
and  and separate "file"-level Solr records for each file in the directory. These different record types could be stored in the same Solr core,
or  or sent to separate Solr cores.o Generation of product metadata from Solr documents.

Viceversa, when a client queries the File Manager for product information, result documents are retrieved from Solr and must be transformed
into transformed into product objects that are presented back to the client. By default, the Solr File Manager will generate a single product for each
Solr each Solr result document, based on the inverse rules that were used to generate the Solr document in the first place.

Alternatively, a project may provide its own
product own product generation algorithm by implementing the ProductDeserializer interface, in a way that is consistent with its own implementation of the
the ProductSerializer interface.

Configuration
-------------

...