About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


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.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
indexing:solrmarc:custom_java_best_practices [2017/01/23 21:29] demiankatzindexing: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 page only applies to SolrMarc 3.0 and later, which was bundled with VuFind 3.1 and later.+:!: This page only applies to SolrMarc 3.0 and later, which was bundled with VuFind® 3.1 and later.
  
 When using custom Java indexing code, the following best practices will make your life easier: When using custom Java indexing code, the following best practices will make your life easier:
Line 8: Line 8:
   * 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.   * 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 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://github.com/vufind-org/vufind/blob/master/import/index_java/src/org/vufind/index/ConfigManager.java|ConfigManager]] used by, among other things, the [[https://github.com/vufind-org/vufind/blob/master/import/index_java/src/org/vufind/index/FullTextTools.java|FullTextTools]].+  * 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://github.com/vufind-org/vufind/blob/dev/import/index_java/src/org/vufind/index/ConfigManager.java|ConfigManager]] used by, among other things, the [[https://github.com/vufind-org/vufind/blob/dev/import/index_java/src/org/vufind/index/FullTextTools.java|FullTextTools]].
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
indexing/solrmarc/custom_java_best_practices.1485206979.txt.gz · Last modified: 2017/01/23 21:29 by demiankatz