Warning: This page has not been updated in over over a year and may be outdated or deprecated.
indexing:solrmarc:custom_java_best_practices
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
indexing:solrmarc:custom_java_best_practices [2017/01/23 21:24] – created demiankatz | indexing:solrmarc:custom_java_best_practices [2023/11/28 19:56] (current) – demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== SolrMarc: Custom Java Best Practices ====== | ====== SolrMarc: Custom Java Best Practices ====== | ||
- | :!: This applies to VuFind | + | :!: This page only applies to SolrMarc 3.0 and later, which was bundled with VuFind® |
+ | |||
+ | When using custom Java indexing code, the following best practices will make your life easier: | ||
+ | |||
+ | * Create small classes containing related functionality for ease of maintenance. SolrMarc will find and compile all of the classes that you place under the import/ | ||
+ | * Use distinctive method names; if you have the same method name in multiple classes, you will have to disambiguate the class name in your marc.properties file. Using distinctive names makes the shorthand syntax more reliable. | ||
+ | * If your custom code needs to access public methods from the core SolrIndexer class, use SolrIndexer.instance() to reach them. | ||
+ | * If your custom code needs to cache or persist values, create a thread-safe singleton to encapsulate those values. You can see an example of this pattern in the [[https:// | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
indexing/solrmarc/custom_java_best_practices.1485206684.txt.gz · Last modified: 2017/01/23 21:24 by demiankatz