Hi @Heryk,
In most cases, Specify will look for the view definition named exactly as the table is (in your case, Specify is looking for the Taxon
view definition, ignoring Taxon2
):
See this section of the “Editing Forms in Specify” doc:
View Definition Names
In most cases, the table has the same view name as its default view (e.g. Collection Object will display the view definition named
CollectionObject
, Accession will displayAccession
, and Collecting Event will displayCollectingEvent
).Some tables use a special name for the view definition that is not always the same as the name of the table. The entire list of such cases are included below:
Table Name Default View Name Attachment AttachmentsForm
Collecting Trip CollectingTripForm
Journal JournalForm
Other Identifier OtherIdentifiers
FieldNotebookAttachment ObjectAttachment
FieldNotebookPageSet ObjectAttachment
…
Because there is a default Taxon
form, it uses that instead of the one you’ve defined. The reason there is the possibility to name a view definition is for cases where you need to reference them as a viewname=""
when editing the XML for a subview (e.g. Determination
or Preparation
).
If you create a view definition named “Taxon” in the appropriate collection/discipline app resource directory, you should see the custom form! Can you let me know if you have any issues after trying this?
Thank you!