Ability to populate buckets using reports or upload

[Ruth Frasur Davis]

It would be useful to have the ability to upload a batch file into the copy buckets management screen similar to what is available in the Item Status screen and/or populate buckets using reports. These possibly should be separate bugs.

Using Evergreen 2.2(.2 )

[Ruth Frasur Davis (redavis)]

Yay!

On Fri, May 9, 2014 at 1:55 PM, Kathy Lussier <email address hidden>wrote:

> ** Changed in: evergreen
> Importance: Undecided => Wishlist
>
> ** Changed in: evergreen
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1208093
>
> Title:
> Ability to populate buckets using reports or upload
>
> Status in Evergreen - Open ILS:
> Triaged
>
> Bug description:
> It would be useful to have the ability to upload a batch file into the
> copy buckets management screen similar to what is available in the
> Item Status screen and/or populate buckets using reports. These
> possibly should be separate bugs.
>
> Using Evergreen 2.2(.2 )
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1208093/+subscriptions
>

--
Ruth Frasur

[Josh Stompro (u-launchpad-stompro-org)]

Quote from tsbere on IRC
" tsbere has had two thoughts on the populate a bucket from a report bit, one for "when the report is run" and the other "from the report output""

I prefer the when the report is run option. So that scheduled reports can automatically create buckets when run.

 It could be an output selection option like html,excel options. Then have the user specify the new bucket name, bucket type, and a drop down of the column name that supplies the ID needed, or just require that the first column be the ID column when you want a bucket produced.

Some macros would be nice for the bucket name, so it can be set to the report name if wanted, or just to add a date entry to the name.

Maybe an option for situations where the results go into an existing bucket to allow for either appending results or overwriting the contents of the bucket.

The new bucket name and ID could be added to the output summary report.

Josh

[Ruth Frasur Davis (redavis)]

I agree with preferring this to happen when the report is run and that having it as an output option would be useful and elegant.

[Thomas Berezansky (tsbere)]

For completeness sake on my thoughts:

I am unsure about *making* buckets from reports. I can see arguments for and against that. On one hand you get a nice clean bucket, on the other hand creating new buckets every time a scheduled report runs seems a bit excessive. And problematic if you don't tell it to include a date/time stamp in the bucket name, for that matter, or if you want to point people who don't get the report output at the bucket.

Providing an existing bucket ID and checking "does the user have permission to write to it" makes more sense to me, especially as then you can throw more than just staff client buckets at it (say, publicly linked bookbag buckets) fairly easily and the "most recent" bucket won't be constantly changing on recurring reports.

As for why I had two thoughts on the timing:

1 - When the report is run - This has direct backend DB access already so it should be faster and, hopefully, more efficient. But I would think we would need to check permissions at this point and bucket ownership would be limited to the report runner. An option to empty the bucket, or perhaps "set" the bucket to the report contents (remove things that are there but not in the report output, leaving the ones that are already there for added date purposes) could be useful for things like new materials bookbags in this case.

2 - From the report output (HTML view, specifically) - While less efficient in some ways this would allow for pick-and-choose (via checkboxes), adding to multiple buckets, or for people *other* than the report runner to add to buckets. Then a single report could be run for multiple people, and each could move things into buckets of their own. This would, IMO, also go better with making the various pieces of information into appropriate links (catalog links for bib ids, item information/editing for copies...) which could help with other staff tasks that don't lend themselves as nicely to the use of buckets.

I suppose there is also the option of *both* as I assume that adding the code to identify bucket-worthy information would be usable both in a "populate this bucket now" and in "put interface elements for populating a bucket later and other such tasks into the HTML output" and thus there would be significant overlap.

[Terran McCanna (tmccanna)]

Not yet available in the web client, but it would still be very useful.

[Irene Patrick (iepatrick)]

I would also find this very useful. I occasionally need to edit items in batch, and I do it infrequently enough that I never can remember the steps I used previously. I always find myself going to the Item Buckets screen and looking all over for a place to upload a file of barcodes. It's only after spending some time looking for a feature that isn't there, that I remember I have to go to Item Status to upload the barcode file, and then add the barcodes to the bucket from there.

I will also add that it has become a hassle today, because the file of barcodes contains 2313 barcodes. So far, I have not been able to find a way to load more than 500 barcodes at a time from Item Status into a bucket. However, it's no problem (besides being slow) to upload the file into Item Status. If I could upload the file directly through the Item Bucket screen (uploading all 2300+ barcodes at once), and not have to go through Item Status first, it would save a huge amount of time.

[Irene Patrick (iepatrick)]

Apologies, I think the issue with saving items from Item Status to a bucket was being caused by memory limitations on my laptop. I did finally get it to work. However, that still does not change the fact that it would be simpler if we could upload a file directly to the Item Bucket, rather than having to go through Item Status first.

[Elaine Hardy (ehardy)]

I do find that transferring large numbers of items from item status to an item bucket can be problematic. I have my item status list display set to all and that does help; however, since it can take a lot of system/workstation time and resources to load a large file into item status and then transfer it, it is not unusual that it hangs, times out, or gremlins attack and item status resets. Then you have to try loading that file again because item status is ephemeral and the transfer failed. I do sometimes break the file into manageable pieces.

Having the ability to load either a file or a report directly into copy bucket (and record buckets, but that is a different bug), would be very helpful. Being able to do both would be wonderful -- a file of barcodes or a report.

[Tiffany Little (tslittle)]

Noting that being able to upload from a CSV straight to a bucket is still desired circa 3.11-3.12. For me I'm not as concerned about uploading directly from a report, but the functionality for uploading a csv of barcodes already exists. It seems silly to have to introduce that middle step of uploading to Item Status and *then* adding to a bucket when we can cut out that middleman of Item Status altogether (when needed).

I'm going to change this back to Confirmed based on others' thoughts and mine, but if we need another bug spun off specifically for CSV upload in buckets rather than also mixing in the reports idea, I can make one of those instead.

[Ruth Frasur Davis (redavis)]

ECDI has contracted with Equinox Open Library Initiative to write specifications for the first part of a buckets overhaul project. This first part includes the ability to upload directly from .csv or .txt to populate a record bucket. This ticket has been identified for inclusion in the next part of the buckets overhaul project (after record buckets).