I was just thinking about this as I was working. Maybe switch to a "re-analyse" button.

Also, a back button or bread crumbs would be nice too. As I am working, I keep looking for it.

Yes I think so.

Remind me... this is the workflow for "updating" a collection that's had an additional crawl:

• i.e. user analyzes collection and is happy;
• additional crawl happens at Archive-It;
• they update their archive-it collections on the user page;
• and then goes back to collection and hits "Analyze Collection" to add in the extra crawl.

Maybe if there's a collection analyzed we could change the text to read "Update Collection"?

This is a good question! My initial reaction is yes.

There have been times when I've selected a handful of collections to analyze, but then forget which ones I've already done, so I know I've hit analyze multiple times on a single collection.

Hidding the button (if returns true) would certainly help with reducing the number of time a user would click unnecessarily.

I like @ianmilligan1 suggestion of an "Update Collection" text if possible

From the technovation mentoring stuff, I learned a bit about doing some quick UI using paper screen shots. I think it might be useful to run some brief user tests with some grad students and other history-friendly folk who aren’t familiar with what we are doing.

@ianmilligan1 "Update Collection" would just run the same job again if there was no "re-seed" update. That's why I was thinking of just hiding it for now because "Update" would be misleading IMO.

@ruebot Agreed.. and if they ran the "re-seed" update, would the "Analyze Collection" button reappear?

@ianmilligan1 we theoretically could. Off the top of my head, we'd just have to start keeping track of the number of times the seed jobs, and analyze ran for a user, and align them. Probably a better way to do it. But, that's not an easy implementation off the top of my head.

Now that we have the collection_queued helper with 6da2791, it's trivial to hide the button. That way we won't run into folk clicking it multiple times, and queuing up the same collection multiple times in a row for analysis.

If y'all are cool with it, I can proceed with hiding the button if collection_queued meets a criteria.

Yes, let's do that!

sounds good!