Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the actionable value of loaded to "autoload" rather than NULL for the catalog record bulkloader #3436

Closed
Jegelewicz opened this issue Feb 16, 2021 · 23 comments
Labels
Function-DataEntry/Bulkloading Help wanted I have a question on how to use Arctos

Comments

@Jegelewicz
Copy link
Member

main bulkloader

If you mean the catalog record bulkloader, these are fundamentally different tools. The catalog record bulkloader is an independent tool - things in it load or error, that's it. "Component loaders" can have dependencies - things can hang around with 'autoload: ....' for weeks, then be processed after related data becomes available. That is, component loaders have three exits:

  • load worked (so delete)
  • load didn't work because data are a mess (so a person needs to become involved)
  • load didn't work because dependent data are MIA (so try again later, no humans required)

I would be in favor of changing the actionable value of loaded to "autoload" rather than NULL for the catalog record bulkloader, but that should be addressed in a new issue.

Originally posted by @dustymc in #2974 (comment)

@Jegelewicz
Copy link
Member Author

For consistency with component bulkload tools.

@Jegelewicz Jegelewicz changed the title Chang the actionable value of loaded to "autoload" rather than NULL for the catalog record bulkloader Change the actionable value of loaded to "autoload" rather than NULL for the catalog record bulkloader Feb 16, 2021
@Jegelewicz Jegelewicz added this to the Needs Discussion milestone Feb 16, 2021
@Nicole-Ridgwell-NMMNHS
Copy link

I'm in favor of this. I've only just started using the catalog record bulkloader, and having the loaded value be null was a bit confusing.

@dustymc
Copy link
Contributor

dustymc commented Feb 18, 2021

Yep, I still like this. Along with everything else, "autoload" doesn't look like any number of whitespace characters in various UIs.

The change would be pretty simple to implement, perhaps a couple days to chase everything down and update documentation.

MAYBE we should expand this (the finding is much of the work) and also talk about the field name - the component loaders use "status."

And "collection_object_id" shares a name with some unrelated stuff and has been confusing at times, if we want one more expansion.

@Jegelewicz
Copy link
Member Author

I like changing to "status". "loaded" implies that something has happened already.

@Nicole-Ridgwell-NMMNHS
Copy link

I like changing to "status".

Agreed.

@campmlc
Copy link

campmlc commented Feb 20, 2021 via email

@dustymc dustymc modified the milestones: Needs Discussion, Next Task Jul 22, 2021
@dustymc
Copy link
Contributor

dustymc commented Sep 2, 2021

See also #3764

Bulkloader will have two actionable status values (and I don't care what the values actually are, HELP!):

  • autoload_core: replaces current NULL functionality, loads the stuff in table bulkloader
  • autoload_extras: autoload_core, plus also set all "component loaders" with the shared UUID to autoload

@Jegelewicz
Copy link
Member Author

Those terms seem good to me.

@dustymc
Copy link
Contributor

dustymc commented Oct 6, 2021

This is running at test.

Essentially everything involving table bulkloader and it's derivatives (bulkloader_stage, pre_bulkloader, bulkloader_for_download) has been touched and should be tested.

Other than the new field label (loaded is now status) and actionable values (status=="autoload_core" does what loaded==NULL used to do, status=="autoload_extras" also changes "components"), the only significant UI change (so far!) is that the mark button:

Screen Shot 2021-10-06 at 8 59 10 AM

now leads to a multiple choice form.

Screen Shot 2021-10-06 at 8 59 22 AM

Please also use this as an opportunity to check out the new data entry and edit screens - the old combo screen may not survive the next change!

TODO: Documentation needs cleaned before/as this goes to production.

@dustymc
Copy link
Contributor

dustymc commented Oct 8, 2021

docs updated

@DerekSikes
Copy link

DerekSikes commented Oct 12, 2021 via email

@Jegelewicz
Copy link
Member Author

Please also use this as an opportunity to check out the new data entry and edit screens - the old combo screen may not survive the next change!

This needs an announcement and some time to let everyone get ready...?

@Jegelewicz Jegelewicz reopened this Oct 12, 2021
@dustymc
Copy link
Contributor

dustymc commented Oct 12, 2021

How do I know

https://handbook.arctosdb.org/documentation/bulkloader.html#processing

announcement and some time

#3691

@campmlc
Copy link

campmlc commented Oct 12, 2021 via email

@DerekSikes
Copy link

DerekSikes commented Oct 13, 2021 via email

@dustymc
Copy link
Contributor

dustymc commented Oct 13, 2021

I don't know how to be more clear than #3436 (comment) - can someone else chime in here, maybe help clarify the documentation?

@dustymc dustymc added the Help wanted I have a question on how to use Arctos label Oct 13, 2021
@campmlc
Copy link

campmlc commented Oct 13, 2021 via email

@DerekSikes
Copy link

DerekSikes commented Oct 13, 2021 via email

@Jegelewicz
Copy link
Member Author

I need to load specimen records.

Are there any "extras" associatied with these records (parts with attributes, multiple identifications, locality attributes)?

If not

Once a record is marked to load by making status “autoload_core” (loads data from table bulkloader)

I there are:

“autoload_extras” (also marks UUID-linked records in “component loaders” to autoload), a script periodically attempts to parse the record into the normalized core Arctos structure. This may result in two things: * the record is created and marked for cache refresh, or * an error is returned in the status column

Does that help?

@DerekSikes
Copy link

DerekSikes commented Oct 14, 2021 via email

@Jegelewicz
Copy link
Member Author

We have parts for each record and they have attributes (eg age class = adult)

Age class is a catalog record attribute, which is not an extra. Part attributes would be things like part preservation, part identifier and part location.

In any case, if there are extras, there will be something other than ) in this column:

image

@DerekSikes
Copy link

DerekSikes commented Oct 14, 2021 via email

@Jegelewicz
Copy link
Member Author

Why not just click that one all the time in case there are extras?

I suppose it is possible that someone may want to review the extras or download and add something to them before they get loaded. It is an opportunity to review them in their own space without all the other stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Function-DataEntry/Bulkloading Help wanted I have a question on how to use Arctos
Projects
None yet
Development

No branches or pull requests

5 participants