Task - Simple New Specimen: can we customize fields for data entry?

[AntWeb-org]

Feature or enhancement

Could this be a customizable form where you select and hide fields specific to your data entry workflow, such as repository, life stage, trip code, etc.?

Customized fields can be toggled/locked, while the other fields could be hidden to create a simple/clean form for ease of entry.

The tripcode could parse CE and GA data straight into the CO record from here so we would not have to manually enter CE/GA data into the CO page again.

@bpescador, @chrisgrinter, @rich-keller

Location

Task - Simple New Specimen

Screenshot, napkin sketch of interface, or conceptual description

No response

Your role

No response

[mjy]

It sounds like there are 2 issues. 1- customization; 2- driving a workflow through an initial Tripcode.

For 2, at least, please try using the New collecting event task. Search by tripcode in the top right. Use the "New" button on the right to quickly spawn multiple new collection objects with options for a simple set of attributes. I'm curious as to wether this general approach reflects the workflow you are outlining here?

[AntWeb-org]

I generally database beginning with the Catalog number and not the tripcode. I can see how this route could work but only if the tripcode previously existed in the database. If it is a new CE for a new CO, then I would have to backtrack and select a new task anyway.

I like the simplicity of the SNS. It does not include a host of internal codes and multiple panels, but if the data entered would parse into the CO record that would save time re-typing all verbatim data into the CE and GA fields.

[mjy]

I guess I was refencing this in that workflow:

The tripcode could parse CE and GA data straight into the CO record from here so we would not have to manually enter CE/GA data into the CO page again.

I like the simplicity of the SNS. It does not include a host of internal codes and multiple panels, but if the data entered would parse into the CO record that would save time re-typing all verbatim data into the CE and GA fields.

With this you're approaching what we envisioned for a long time, ways to semi-automatically parse verbatim into various fields.

There are several places this occurs:

• Stepwise determinations (from buffered determinations to determinations, very efficiently)
• Comprehensive COs - After you add a buffered label, you have one-click options to copy and breakdown data.

[AntWeb-org]

Oh yes, "The tripcode could parse CE and GA data straight into the CO record from here so we would not have to manually enter CE/GA data into the CO page again." but I still start with the Catalog number. Basically, if I enter data manually, I enter the the Catalog number, OTU, tripcode (CE and GA data if not previously in DB), life stage, preparation, namespace, repository, type status, det. by and det. date, and two note fields for the specimen and for any DNA notes.

I admit I am not familiar with the buffered portion of TW. What is "buffered" as opposed to the rest of the data? Do I fill in buffered in addition to verbatim, parsed and tripcode in the CSD task?

[mjy]

@debpaul - A bit of priority- let's ensure

What is "buffered" as opposed to the rest of the data? Do I fill in buffered in addition to verbatim, parsed and tripcode in the CSD task?

and related is answered in docs.taxonworks.org

:)