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

remove the old data entry screen #4257

Closed
dustymc opened this issue Jan 13, 2022 · 25 comments
Closed

remove the old data entry screen #4257

dustymc opened this issue Jan 13, 2022 · 25 comments
Labels
Bug Arctos is not performing as it should.

Comments

@dustymc
Copy link
Contributor

dustymc commented Jan 13, 2022

Describe the bug

#4175 is still in process

To Reproduce

Do something with wkt_media_id in the old data entry screen

Expected behavior

Something

What Happens

Nothing

Additional context

WKT and the handling thereof via Media will be gone from next release. I'll leave the field in the bulkloader and "old" screen until we're fully migrated to the new. The loader will ignore wkt_media_id beginning next release.

** ToDo **

Remove the field from everything once there's no longer a UI depending on it.

@dustymc dustymc added the Bug Arctos is not performing as it should. label Jan 13, 2022
@dustymc dustymc added this to the Next Task milestone Jan 13, 2022
@dustymc dustymc changed the title remove wkt_media_id from data entry and bulkloader remove the old data entry screen Jun 3, 2022
@dustymc
Copy link
Contributor Author

dustymc commented Jun 3, 2022

Unless there's some compelling reason not to, I'll finalize removing the old data entry screen sometime after 2022-07-03.

  • remove wkt_media_id from data entry and bulkloader
  • clean up templates (and everything without enteredby)
  • revisit structure/requirements

@Jegelewicz
Copy link
Member

@lin-fred @ewommack can we make a few announcements about this?

@ewommack
Copy link

Sorry just coming back online and going through my emails. I was still able to get to the old data entry screen, so we still have it live for now?

@dustymc
Copy link
Contributor Author

dustymc commented Jul 28, 2022

I'm waiting for an announcement, this isn't urgent to me (that could quickly change), but it may be to someone who's invested a lot of work into something the old screen won't finalize.

Also semi-merging #4801 here - collection_id should be removed from the bulkloader, that will likely be entirely fatal to the old screen.

$fields don't play nice, rename them

@DerekSikes
Copy link

DerekSikes commented Jul 29, 2022 via email

@AJLinn
Copy link

AJLinn commented Jul 29, 2022

Is everyone happy with the new screen? For me, it's far less user friendly.

I was very used to the old one, ignoring what was not relevant.
My staff person who has the visually-induced migraines hates the new one.
My other staff person loves the new one, especially the ability to customize the layout and save templates.

is there any functional reason why we can't allow folks to continue to use the old one if they like it, while allowing those who like the new one to use it?

@dustymc
Copy link
Contributor Author

dustymc commented Aug 1, 2022

functional reason why we can't allow folks to continue

Yes, the old screen is technically dodgy, see #3691 and #2974 and probably others.

retains the look

Not quite sure what this means, but #4874 maybe

& arrangement

You can put anything anywhere. However you had the old set up, you should be able to get very close to that in the new.

fit in the same pixel dimensions

You can put stuff wherever you want, and you have much better control of what's visible. You determine the footprint, it should be completely trivial to make it much smaller than the old.

techs can change things,

I don't understand the problem in that?

https://www.youtube.com/watch?v=QJeLNCn62dE

@sharpphyl
Copy link

We like the new format: the ability to customize each section on the fly, save profiles (and incomplete entries). The old format was visually easier to follow, but perhaps the appearance could be enhanced without impacting the functionality.

@ewommack
Copy link

ewommack commented Aug 1, 2022

& arrangement

You can put anything anywhere. However you had the old set up, you should be able to get very close to that in the new.

fit in the same pixel dimensions

You can put stuff wherever you want, and you have much better control of what's visible. You determine the footprint, it should be completely trivial to make it much smaller than the old.

Maybe it would help if we created a profile that everyone could access that was as close to the format of the old screen as we could get? And maybe color that one green?

@campmlc
Copy link

campmlc commented Aug 1, 2022 via email

@dustymc
Copy link
Contributor Author

dustymc commented Aug 1, 2022

old format was visually easier to follow

Elaborate please.

profile that everyone could access that was as close to the format of the old screen

Screen Shot 2022-08-01 at 12 39 12 PM

color

#4874

Pull function restored

It is and has always been there.

@ewommack
Copy link

ewommack commented Aug 1, 2022

Elaborate please.

If we created a profile for the new data entry screen and labeled it "Historic Arctos Data Entry - all collections" or something would it be something that would help @AJLinn's students and others who prefer the old screen?

And I did just read through #4874 - you're so on top of things @dustymc !

@campmlc
Copy link

campmlc commented Aug 1, 2022

Apparently the pull function is only missing from the new screen in Browse and Edit? But it is present in the Old Edit screen?
Screenshot 2022-08-01 14 01 31

vs

Screenshot 2022-08-01 14 01 41

@DerekSikes
Copy link

DerekSikes commented Aug 3, 2022 via email

@dustymc
Copy link
Contributor Author

dustymc commented Aug 3, 2022

Yes, the layout is by pixels, different environments have different capabilities, probably-slight adjustments are to be expected.

Yes, there are no limitations on where elements may be placed - cover whatever you want (elements will pop to the front when you click on them), leave seldom-used things outside the normal viewpoint, WHATEVER. That's the point, you can set it up however you want, you don't need to be limited by how I think you should be working.

Here are the two screens on my machine at the moment, but that probably has little to do with what you need to see or your screen layout. There are more screenshots in #3691.

Screen Shot 2022-08-03 at 8 15 26 AM

Screen Shot 2022-08-03 at 8 15 12 AM

@DerekSikes
Copy link

DerekSikes commented Aug 3, 2022 via email

@Jegelewicz
Copy link
Member

a way to reduce the size of the attributes panel to show only 3 or 4 rows?

customize and only allow for 3 or 4 rows

why is the Collection Object Remark field so large?

Just use the little expander at the bottom right corner to make it smaller

image

@dustymc
Copy link
Contributor Author

dustymc commented Aug 3, 2022

reduce the size of the attributes panel .. 3 or 4 rows

Screen Shot 2022-08-03 at 10 17 44 AM

Screen Shot 2022-08-03 at 10 18 07 AM

results in

Screen Shot 2022-08-03 at 10 18 16 AM

you can also eg
Screen Shot 2022-08-03 at 10 18 32 AM

for

Screen Shot 2022-08-03 at 10 18 39 AM

if there's some column(s) that you don't use somewhere.

why is the Collection Object Remark

Someone asked for it to be (maybe @AJLinn) - you can grab a corner and shrink it

Screen Shot 2022-08-03 at 10 20 57 AM

Dammit @Jegelewicz ....

@Jegelewicz
Copy link
Member

Heh heh heh....but you added better visuals....

@DerekSikes
Copy link

DerekSikes commented Aug 3, 2022 via email

@DerekSikes
Copy link

DerekSikes commented Aug 3, 2022 via email

@AJLinn
Copy link

AJLinn commented Aug 4, 2022

Someone asked for it to be (maybe @AJLinn) - you can grab a corner and shrink it

yes, I asked for that. Prior to the change it was only one very small non-expanding line and we regularly add a lot of info to that field when cataloging. I agree with Derek it would be useful if those expandable fields could be saved at an expanded or un-expanded size per user (e.g. our attribute description field gets a ton of info and we always have to manually expand it each time we catalog an item).

@DerekSikes
Copy link

DerekSikes commented Oct 11, 2022 via email

@dustymc
Copy link
Contributor Author

dustymc commented Nov 2, 2022

merge-->#5193

We can't seem to preemptively kill this thing, it can die an evolutionary death.

@dustymc dustymc closed this as completed Nov 2, 2022
@ewommack
Copy link

ewommack commented Nov 2, 2022

it can die an evolutionary death

So eventually it gets so clunky and poor at its job everyone switches over?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Arctos is not performing as it should.
Projects
None yet
Development

No branches or pull requests

7 participants