Component Loaders and Unloaders

Component Loaders are an ecosystem of tools which work asynchronously, and so therefore can generally deal with any number of operations without fear of overwhelming the always-limited infrastructure.

Adding Data

All Component loaders may be directly interacted with, and each will provide a data template (which is also the only authoritative source of information). Additionally, there are many UI shortcuts which write to component loaders. An API is possible but not implemented as of this writing.

Keys

Component loaders generally follow the Arctos Identifier Convention.

Status

Every component loader has a ‘status’ column. A value of autoload indicated the record is ready for processing; any other value will be ignored. It is usually possible to load data with status to the loaders, providing a mechanism to beging processing immediately.

Success

A successful run generally results in the record being deleted from the tool. A few lookup tools do not follow this model; such behavior is documented in the tools.

Errors

Occasionally a cryptic error will be returned in status; contact us for help.

Permissions

Permissions vary across tools, but manage_records is generally required for bulk operations. Users with this role are expected to have a GitHub address; those without may have problematic data transferred to CSV without notice.

Order of Operations

A UI which provides comprehensive runtime information, and allows user-based intra-tier sorting, is available.

Tiers

See https://github.com/ArctosDB/dev/issues/507; tiers are no longer available, all run order is user-controlled.

General Guidelines

Edit this Documentation

If you see something that needs to be edited in this Documentation, you can create an issue using the link under the search widget at the top left side of this page, or you can edit directly here.