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 wording - Bulkload Specimen Event to Bulkload Catalog Record Event #5497

Closed
ebraker opened this issue Jan 18, 2023 · 14 comments
Closed
Labels
Priority-Normal (Not urgent) Normal because this needs to get done but not immediately.

Comments

@ebraker
Copy link
Contributor

ebraker commented Jan 18, 2023

This page still uses "specimen":
https://arctos.database.museum/tools/BulkloadSpecimenEvent.cfm

Can we change to Catalog Record?

@ebraker ebraker added Priority-Low (Wish list) I don't want to forget this, but it doesn't need to be done immediately Specimen to Collection Object labels Jan 18, 2023
@Jegelewicz
Copy link
Member

Jegelewicz commented Jan 18, 2023

That title currently comes from

#thisFormName#

and the form name is

Bulkload Specimen Event

so either I have to hard code the title (which I can do) or the form name needs changing (which I cannot?)

@dustymc your call

@Jegelewicz
Copy link
Member

See also #4460

@dustymc
Copy link
Contributor

dustymc commented Jan 18, 2023

I'm hesitant to break the implicit link between internal "advanced user" UI and eg the table browser. The table is clearly poorly named and I'm not defending anything, I'd just like to confuse people as little as possible and I think renaming/retitling this would confuse some users.

We really need a policy on this. Renaming database structures is a huge pain, but this particular table just keeps popping up and taking a week to rename and rebuild it and everything it touches might have actually saved some time. That's not the only possibility, but it might be the most radical and it's not seeming very radical at the moment. (Of course finding a spare week is a whole nuther matter.)

See also #4707 - good opportunity to rename some stuff (hopefully not to something that'll need renamed in a bit!) in there.

@dustymc dustymc added this to the Needs Discussion milestone Jan 18, 2023
@Jegelewicz
Copy link
Member

It was decided long ago that we should "de-specimen" Arctos. I would REALLY like to see the removal of "specimen" for the cultural collections, we need to do this.

@Jegelewicz Jegelewicz added Priority-Normal (Not urgent) Normal because this needs to get done but not immediately. and removed Priority-Low (Wish list) I don't want to forget this, but it doesn't need to be done immediately labels Jan 18, 2023
@Jegelewicz
Copy link
Member

Renaming database structures is a huge pain

So we need to be careful when we create new ones? This seems to have been a somewhat ad-hoc adventure, but maybe we need to carefully consider what we name tables/fields going forward? See also #5326

@dustymc
Copy link
Contributor

dustymc commented Jan 18, 2023

careful when we create new ones?

Yes, that's the sort of thing the admin arm of Arctos should be dealing with (in a timely manner) so I don't have to. Or I could just name everything whatever generateUUID() spits out....

@Jegelewicz
Copy link
Member

So - process matters here. We need a little time to consider these things and we have to get community input. Perhaps we need a request form just like we have for code tables. What do you need from us when a new field or table is added?

@Jegelewicz
Copy link
Member

How about this?

/SpecimenDetailResponsive.cfm

instead could we have

/RecordDetail.cfm

?

@dustymc
Copy link
Contributor

dustymc commented Jan 18, 2023

need a little time

Yes, but there has to be some sort of linear progression to a finish. We get distracted, move on to the next thing, rope tangentially-related stuff in, etc., etc. That's probably all got to be considered, but it can't be a distraction either. IDK how to do that....

What do you need

Start with the policy. I sound like a broken record on that of late, but it's what matters.

How about this?

That's a temporary URL - it'll just be /guid/... (which is why I panicked a bit when it was suggested we keep the old stuff for a while yesterday - that and I can't clean up some things that desperately need cleaning while I have to keep the old stuff functional).

@ewommack
Copy link

@dustymc - the Diversity and Inclusion Committee would like to help develop and move forward the process of making the language and shared areas of the Arctos database more inclusive.
We are not proposing changes or renaming things, but first want to understand where things are with the use of the word "specimen" across the website.

Could we start with a list of all of the places in Arctos (tables, column names, page names, fields, etc.) that use "specimen" in some way please? I know we've been changing a number of them for a bit (#3780), but could we get material that is also behind the scenes that only you can see?

Once we have the list, the committee feels we'll have a better understanding of where we are using the word presently. Understanding would be a good place to start to figure out the best way to move forward. And hopefully not result in you having to change things piece-meal.

@ewommack
Copy link

Hi @dustymc - just checking if this might a possible ask? The committee would be happy to work on that list if we could get it.

@dustymc
Copy link
Contributor

dustymc commented Sep 19, 2023

material that is also behind the scenes that only you can see

I was under the very firm impression that behind-the-scenes stuff is not to be involved in this process. @mkoo

@ewommack
Copy link

I probably used the wrong terms. Would it be possible to get a current list of all of the places in Arctos that use the term "specimen"?

No behind the scenes things, but not sure if this is possible in your magic @dustymc powers.

@Jegelewicz
Copy link
Member

The first comment has been resolved and is now

https://arctos.database.museum/loaders/BulkloadSpecimenEvent.cfm

but looks like this

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority-Normal (Not urgent) Normal because this needs to get done but not immediately.
Projects
None yet
Development

No branches or pull requests

4 participants