Request - deprecate bulk record-event updater

[dustymc]

Help us understand your request (check below):

• other

Describe what you're trying to do

The tool found under search-->Tools -> Manage --> Record-Events is of a type which has caused multiple outages, and generally just doesn't play nicely with our current architecture.

I don't think this particular tool has actually crashed anything, so there's some time to plan. Please help me understand the functional needs if you use this tool.

The tool already produces CSV suitable for the record-event bulkloader. Is the current loader capable of doing whatever needs done here, does it need improved, do we need some new tool, ???

(Source: #264)

[Jegelewicz]

The tool already produces CSV suitable for the record-event bulkloader. Is the current loader capable of doing whatever needs done here, does it need improved, do we need some new tool, ???

Sometimes you just need to correct or update record event remark, you don't want to create a whole new event. That is why this tool exists and I have used it rather recently. If we had a bulk update tool for record event remarks that would allow for the same action but put it into the component loader instead of the somewhat invisible search results tool. This would require some way to designate which record event you want to update, but seems like that should be possible.

[dustymc]

update ... create

A tool to update only...

arctosprod@arctos>> \d specimen_event
                                              Table "core.specimen_event"
        Column         |            Type             | Collation | Nullable |                  Default                  
-----------------------+-----------------------------+-----------+----------+-------------------------------------------
 specimen_event_id     | integer                     |           | not null | nextval('sq_specimen_event_id'::regclass)
 collection_object_id  | integer                     |           | not null | 
 collecting_event_id   | integer                     |           | not null | 
 assigned_by_agent_id  | integer                     |           | not null | 
 assigned_date         | timestamp without time zone |           | not null | 
 specimen_event_remark | character varying(4000)     |           |          | 
 specimen_event_type   | character varying(60)       |           | not null | 
 collecting_method     | character varying(4000)     |           |          | 
 collecting_source     | character varying(60)       |           |          | 
 verificationstatus    | character varying(60)       |           |          | 
 habitat               | character varying(4000)     |           |          | 
 verified_by_agent_id  | integer                     |           |          | 
 verified_date         | character varying(30)       |           |          | 

... should be easy enough - that do what's needed?

into the component loader

Yes, that's my need, that system doesn't cause the logjams that the old Oracle-centric tools sometimes do.

invisible search results tool

That can still feed the component loaders (in lots of ways, and pre-filter, and etc., etc., etc.), but yea wouldn't be necessary/would just be one entry point.

designate which record event

https://arctos.database.museum/guid/UCM:Herp:65656?seid=2482606 should be a bit familiar and would do it.

[campmlc]

I was just working on a project yesterday which required I add new events under my name and date with edited specific localities. I needed to do this by finding groups of records in search results and then honing in using Berkeley Mapper to specific sites, and then attempting to add new events for all records for that locality. There were multiple localities. I attempted to figure out the best way to do this using Tools: Manage: Record Events, but that was extremely confusing and didn't seem to give me the tools I needed. I ended up using it to get lists of events for each locality and editing each one separately by editing the locality, which at least corrected several events at once. But this did notadd a new event with my determination. The whole process was extremely difficult to figure out and navigate, and I'm not sure I can replicate what I did. Certainly the records are inconsistent because I tried different approaches to see what might work.
I really appreciate being able to edit individual records or small groups of records in real time through the Tools menu options. That allows me to continue with multi-step workflows without having to interrupt what I am doing for some indeterminate amount time for the bulkloader at each step. But at the same time, it would be best to have a standardized way of adding events, editing events, and editing localities that is usable, consistent, and coherent. Any solution here that enables that would be much appreciated.

[dustymc]

Blocked by #301; going dev.