Versions Compared

Old Version 11

changes.mady.by.user Jim Blake

Saved on

compared with

New Version 12

changes.mady.by.user Jim Blake

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. It enables you to change the Developer Settings without navigating away from your current page.
  2. It provides a visual reminder that VIVO is in Developer Mode. If a production instance were accidentally configured to run in Developer Mode, it would be easily noticed.

No Developer PanelDeveloper Panel (closed)

Image Removed

 Image Added

Entering Developer Mode

...

In the panelAllow anonymous user to see and modify developer settings
In the filedeveloper.permitAnonymousControl
EffectIf true, any VIVO user may change the developer settings. If false, only a system administrator (or root) may change the settings.

The "General" tab

Image RemovedImage Added

Freemarker settings

...

Link textShow background threads
URL/admin/showThreads
The pageDisplays information about the active background threads. These threads may be rebuilding the search index, re-inferencing the knowledge base, or rebuilding the Class Cache.
Link textShow RDF data sources
URL/admin/showSources
The pageDisplays information about the triple stores, and the layers of adapters that the application wraps around them, including ModelMakers, OntModels, etc.

The "Search" tab

Image RemovedImage Added

Search query settings

...

In the panel Restrict by document contents
In the filedeveloper.searchIndex.documentRestriction
EffectSet this to a regular expression. An addition will be logged only if the contents of the documents matches the regular expression, in whole or in part.
In the panel Log deletionsbreakdown timings for indexing operations
In the filedeveloper.searchDeletionssearchIndex.enablelogIndexingBreakdownTimings
Effect

Write an entry When an indexing operation completed, write entries to the log showing how much time was taken by each indexing object: Excluders, DocumentModifiers, and UriFinders. Each entry includes

  • The display label of the indexing object
  • The number of times that the indexing object was invoked
  • The total time required for the indexing object
  • The average time for each invocation of the indexing object

In the panel Log deletions
In the filedeveloper.searchDeletions.enable
Effect

Write an entry to the log each time documents are deleted from the Search each time that documens are deleted from the Search index, assuming that INFO-level logging is enabled for the SearchEngineLogger. Each entry includes

  • The time spent deleting the documents
    • Either
  • the list of URIs being deleted, or
    • the search query that was used to find documents for deletion

    the SearchEngineLogger. Each entry includes

    • The time spent deleting the documents
    • Either
      • the list of URIs being deleted, or
      • the search query that was used to find documents for deletion.
    In the panel Suppress the automatic indexing of changed triples.
    In the filedeveloper.searchIndex.suppressModelChangeListener
    Effect

    If this is selected, the search indexer will not automatically adjust to changes in the data model. This means that you can ingest data much more quickly, but you must manually request a full re-indexing when your ingests are complete.

    Note

    This doesn't really belong in the developer panel, since it changes the way VIVO operates. It was put here to answer an urgent requirement.

    Links

    Link textRebuild search index
    URL/SearchIndex
    The pageAllows you to request a rebuild of the search index, and to monitor its progress.

    The "Authorization" tab

    Image RemovedImage Added

     

    In the panelWrite policy decisions to the log
    In the filedeveloper.authorization.logDecisions.enable
    Effect

    Write an entry to the log for each policy decision that is made for any requested action, assuming that INFO-level logging is enabled for the PolicyDecisionLogger. Each entry includes

    • The requested action
    • The name of the policy
    • The decision and message.

    The remaining settings in this area can be used to restrict which queries are decisions are logged, or to include more information for each decision.

    ...