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

Help needed in Arctos: change relationship for identifiers from self to parasite of #8277

Open
campmlc opened this issue Nov 6, 2024 · 3 comments
Assignees
Labels
collection-specific Pertains to a specific collection, and needs feedback or action from the collection staff Component Loader Things involved in Round Five of the component loader discussions Display/Interface I don't like the way Arctos looks or it isn't working for me aesthetically. Priority-High (Needed for work) High because this is causing a delay in important collection work..

Comments

@campmlc
Copy link

campmlc commented Nov 6, 2024

Tell us what you are trying to do

I am trying to fix 94 records that were loaded with the wrong identifier relationship. They should be "parasite of" but they were loaded as "self". I can't find a simple way to do this. Ideally, we'd have a tool like the ones in the Tools menu for search results that would allow Manage for identifiers the same way we allow Manage for identifications, which could be used to modify a single component from the results. Unfortunately for operators, these simple and easy use tools are being deprecated.
In their place we are asked to use the component loader system. The only way I have found to make a change in a single field in the identifier metadata is to unload the existing identifier using the indentifier unloader and then reload the identifier with the updated relationship value in the identifier bulkloader. This has the disadvantage of not only requiring two separate bulkload files prepared and loaded in two different component loaders, with all the corresponding challenges that poses (including component loaders stuck for several days, see #8265 ), but it also results in the loss of all the original identifier metadata as to which student assigned the identifier on what date, replacing it with metadata associated with the new bulkload.
I tried this approach with bulkloading the new identifier value first and it failed - see attached file. I would prefer to load the correct new ID first, and then delete the incorrect one once I confirm the new one successfully loaded. But perhaps Arctos doesn't permit loading the same identifier twice, with the only difference in relationship value? If so, that isn't clear from the error message. If the problem is something else, please help clarify.
I said in a previous issue that this process is challenging, for all the above reasons. I'd love to have a process or tool that would make this simple, as it would be if we could use the Manage tool in search results. Please advise.

cf_temp_oids_download.csv

identifier rebulkload to fix 94 records from self to parasite of.csv

identifierUnloader bulkload to fix self to parasite of 94 records.csv

What are relevant pages in Arctos

Provide a link to or a description of the page where you need help.

@campmlc campmlc added Priority-High (Needed for work) High because this is causing a delay in important collection work.. Component Loader Things involved in Round Five of the component loader discussions User experience Issues related to user experience difficulties labels Nov 6, 2024
@dustymc
Copy link
Contributor

dustymc commented Nov 6, 2024

This format is difficult to extract functional needs from, but I'll try.

The frustrations could possibly be directed to https://github.com/ArctosDB/internal/issues/330 - I don't have any influence over the resources I have available and don't get invited to the meetings of those who do (I believe you do and would know this). I will happily make use of any resources that are made available to me, but I also can't advocate for tools which demonstrably cause problems with the resources I actually have, and sometimes those resources mean less availability than I'd like.

There is also a social aspect to this - eg the unloader file (the format suggests you've found that??) could write directly to the unloader tool, even with status==autoload, but my intuition is that this would not be understood and so would have great potential to be catastrophic.

In any case, I believe you've found the unloader, if not the path is

  • search
  • tools/identifiers
  • filter as necessary
  • download for unloader (button)
  • upload to unloader (the extra step necessitated by my social concerns above)
  • set to autoload (could also be done in CSV before upload)

The loader is a very tiny bit more involved, this could be changed but I'd need specifics and The Community would need to weigh in - there's clearly a cost to complexity (eg people getting lost and doing the wrong thing). This writing directly to a loader would be a bit less terrifying, someone clicking the button 17 times would just get one (easily removed via the above if wrong) identifier and 16 errors. The process here is:

  • search
  • tools/identifiers
  • filter as necessary (you're already here if coming from the unloader)
  • download identifiers (button)

Then the CSV will need manipulated (that could change, see above). In your case this involves:

  • remove the TRIPLET column
  • change the ID_REFERENCES column (from self to parasite of here)
  • rename the OTHER_ID_TYPE column to new_other_id_type
  • rename the DISPLAY_VALUE column to new_other_id_number
  • remove the DESCRIPTION column
  • remove the ASSIGNED_BY column
  • remove the ASSIGNED_DATE column
  • remove the ISSUED_BY column
  • rename the ISSUED_BY_AGENT column to issued_by
  • remove the ASSIGNED_BY_AGENT column

upload to identifier loader.

In your attached file, you're trying to use the thing that probably should have just unloaded to find the record - and it's ambiguous, you can check via https://arctos.database.museum/search.cfm?oidtype=Arctos%20record%20GUID&oidnum=%3Dhttps%3A%2F%2Farctos.database.museum%2Fguid%2FMSB%3AMamm%3A293218

Using the GUID should be stable, easy, and unambiguous, definitely what I'd recommend.

@dustymc dustymc added this to the Community Forum milestone Nov 6, 2024
@campmlc
Copy link
Author

campmlc commented Nov 6, 2024

This request is that we need a simpler tool which already exists for other data types, including accessions and identifications. These tools are the ones found under Manage in Search Results Tools menu. I am requesting a similar tool for manage identifiers, one that does not directly require me to deal with the component loader system.

I've been using the Manage Accessions tool all morning, and it is simple and does exactly what I need in seconds, without my having to stop my existing workflow and dedicate my full attention to creating two separate bulkload files, waiting the several days necessary to get the data loaded and unloaded through the component loaders. Having attempted the latter without the ability to give it my entire concentration for a couple hours, I've made several mistakes which are going to require my additional complete attention for several hours. Surely we can make this easier for operators?

@campmlc
Copy link
Author

campmlc commented Nov 7, 2024

Here is something that hopefully can provide more detail on functional needs using the component loader system. This is still far more complex that merely adding a "modify existing identifers" tool to the Manage section in search results, but maybe it will show a path to what I am trying to do.

  1. Conduct a search
  2. Click on Tools Menu
  3. Go to View/Download Identifiers
  4. Filter for Arctos Record Guid identifier type (to find relationships between records)
  5. End up at https://arctos.database.museum/Reports/identifier_download.cfm, see screenshot attached.
    From the screenshot, all I need to do is to modify the existing relationship values for these records from "self" to "parasite of".

On the right side of the page, I don't see an option to be able to modify fields of existing identifiers. This would be ideal. Otherwise, I have to use the identifier unbulkloader to completely remove the values and then use the identifier bulkloader to reload them from scratch, losing all original assigned by metadata in the process.
Is this more clear?
Screenshot 2024-11-06 18 17 35

@mkoo mkoo added collection-specific Pertains to a specific collection, and needs feedback or action from the collection staff Display/Interface I don't like the way Arctos looks or it isn't working for me aesthetically. and removed User experience Issues related to user experience difficulties labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
collection-specific Pertains to a specific collection, and needs feedback or action from the collection staff Component Loader Things involved in Round Five of the component loader discussions Display/Interface I don't like the way Arctos looks or it isn't working for me aesthetically. Priority-High (Needed for work) High because this is causing a delay in important collection work..
Projects
None yet
Development

No branches or pull requests

3 participants