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

Can we get GUID as a column for the bulkload identifiers template #2292

Closed
DerekSikes opened this issue Oct 3, 2019 · 5 comments
Closed
Assignees
Labels
Priority-High (Needed for work) High because this is causing a delay in important collection work..

Comments

@DerekSikes
Copy link

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Other bulkloader templates have a column for GUID but this one

http://arctos.database.museum/tools/BulkloadOtherId.cfm

requires we break GUIDs up into 'GUID_Prefix', 'Existing_other_ID_type', and "existing_other_ID_number"

It would be much easier to just be able to paste a list of GUIDs directly into the bulkloader template, like we can do with many of the others.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Priority
Please assign a priority-label. low

@dustymc dustymc self-assigned this Oct 3, 2019
@dustymc dustymc added this to the Next Task milestone Oct 3, 2019
@sharpphyl
Copy link

Thanks for asking. I referenced at the very end of #2104. It's just extra work and opportunity for error to break up the GUIDs on one bulkload form and combine them on the other one. Having identical fields/headings would be helpful.

@DerekSikes DerekSikes added the Priority-Normal (Not urgent) Normal because this needs to get done but not immediately. label Jun 26, 2020
@sharpphyl
Copy link

@dustymc Has this fallen off the radar? It doesn't look like there was a major issue with making the change. I'm working through changes to a few thousand catalog records to update the other_id type.

First I add the revised ID and I have to separate our guid_prefix (DMNS:Inv:) from the catalog number

Screen Shot 2020-08-14 at 10 57 16 AM

Screen Shot 2020-08-14 at 11 03 20 AM

Then I delete the old ID I wanted to replace and I have to recombine the guid_prefix with the catalog number

Screen Shot 2020-08-14 at 10 56 55 AM

Screen Shot 2020-08-14 at 11 03 11 AM

I know we've had extensive discussions about the three-part numbers, etc. but is there a reason why the headings to add and to delete other identifiers don't use the same headings as Derek requested? I don't care which way, but I'd vote with Derek for GUID.

BTW from a (non-database professional) UI perspective, it would be great if the instructions were more similar in structure such as the order of the columns. That's probably a whole other can of worms.

@dustymc
Copy link
Contributor

dustymc commented Aug 14, 2020

fallen off the radar

No, if there's a milestone it's on the radar, but it hasn't floated to the top yet either. Please feel free to add it to the AWG Issues agenda (or do whatever we do to prioritize....).

don't care which way

It's an addition, not a replacement. I need the non-GUID for various reasons, but the GUID is more reliable and easier and etc. when it's available.

instructions were more similar

#2974 - working on it, all needs prioritized.

@sharpphyl
Copy link

Ok, but I don't deal with AWG issues so I'll leave that to @DerekSikes to determine if the priority warrants it.

@Jegelewicz Jegelewicz added Priority-High (Needed for work) High because this is causing a delay in important collection work.. and removed Priority-Normal (Not urgent) Normal because this needs to get done but not immediately. labels Aug 18, 2020
@dustymc dustymc modified the milestones: Next Task, Active Development Sep 16, 2020
@dustymc
Copy link
Contributor

dustymc commented Sep 16, 2020

Blocked by #2974 (comment)

  1. Develop the template
  2. Confirm it's satisfactory
  3. Proceed with this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

4 participants