[Evergreen-catalogers] Tracking Cataloging Bugs on Cataloging Working Group page

Thu Apr 18 13:15:37 EDT 2013

Glad you reminded me about tagging -- thought of it during someone's
presentation last week. I will add tags as I go back through the bugs as
well.

And I agree Sarah that we also need more specific tags -- For example :
cataloging, fixed field, type

Elaine

________________________________

J. Elaine Hardy
PINES Bibliographic Projects & Metadata Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304

404.235-7128
404.235-7201, fax
ehardy at georgialibraries.org
www.georgialibraries.org
www.georgialibraries.org/pines

-----Original Message-----
From: evergreen-catalogers-bounces at list.evergreen-ils.org
[mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf Of
Sarah Childs
Sent: Thursday, April 18, 2013 12:39 PM
To: evergreen-catalogers at list.evergreen-ils.org
Subject: Re: [Evergreen-catalogers] Tracking Cataloging Bugs on Cataloging
Working Group page

Kathy,
Thanks, that's a great suggestion. I went in and quickly added links to a
few relevant tags to the page: 
http://open-ils.org/dokuwiki/doku.php?id=cataloging.

Since cataloging is such a broad topic, it might be nice to add some more
specific cataloging related tags as well.  We'll have to get to work
classifying and virtually collocating the cataloging bugs and wishlist
items.

---
Sarah Childs
Technical Services Department Head
Hussey-Mayfield Memorial Public Library
250 North Fifth Street
Zionsville, IN 46077
317-873-3149 x13330
sarahc at zionsville.lib.in.us

On 2013-04-18 09:54, Kathy Lussier wrote:
> Hi all,
> 
>  This is great! I think it will benefit everyone if the cataloging 
> bugs (and bugs for other functional areas) are easier to track.
> 
>  I thought I would offer up a suggestion that has made it helpful to 
> track the acquisitions bugs. Rather than re-entering each cataloging 
> bug on a wiki page, have you given any thought to adding a cataloging 
> tag to those bugs in Launchpad? You could then create a link on the 
> wiki page that goes directly to the bugs that have been tagged with 
> cataloging.
> 
>  A while back, Jennifer Pringle went through the LP bugs and added an 
> acq tag to anything that was related to acquisitions. I then put 
> myself in the habit of adding the acq tag whenever I submitted an 
> acquisitions bug, or, if I saw one come through without a tag, I would 
> add it. With that tag, I could then build a link like this one (sorry, 
> it's a little long):
> 
> 
> https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-
> datecreate
> d&s
> earch=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&fie
> ld.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3
> Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_
> RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field
> .bug_commenter=&field.subscriber=&field.structural_subscriber=&field.t
> ag=acq+&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes
> .used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used
> =&field.has_branches.used=&field.has_branches=on&field.has_no_branches
> .used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_b
> lueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
> [12]
> 
>  that lets me see all bugs tagged with acquisitions that have not yet 
> been committed to the code or released, sorted by those that have been 
> most recently submitted. I noticed that a similar tag has been added 
> to authority bugs 
> https://bugs.launchpad.net/evergreen/+bugs?field.tag=authority. [13]
> 
>  I just thought it might help streamline the process of tracking these 
> bugs.
> 
>  Kathy
> 
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> klussier at masslnc.org
> Twitter: http://www.twitter.com/kmlussier [11]
> 
>  On 4/17/2013 8:00 PM, Hardy, Elaine wrote:
> 
>> Thanks Sarah!
>> 
>> I plan on going over the bug requests as I have time over the next 
>> few days and add to the list.
>> 
>> Elaine
>> 
>> ________________________________
>> 
>> J. Elaine Hardy
>> PINES Bibliographic Projects & Metadata Manager Georgia Public 
>> Library Service
>> 1800 Century Place, Ste 150
>> Atlanta, Ga. 30345-4304
>> 
>> 404.235-7128
>> 404.235-7201, fax
>> ehardy at georgialibraries.org
>> www.georgialibraries.org [6]
>> www.georgialibraries.org/pines [7]
>> 
>> -----Original Message-----
>> From: evergreen-catalogers-bounces at list.evergreen-ils.org
>> [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On 
>> Behalf Of Sarah Childs
>> Sent: Wednesday, April 17, 2013 4:25 PM
>> To: evergreen-catalogers at list.evergreen-ils.org
>> Subject: Re: [Evergreen-catalogers] Bug report -- deposit flag hold 
>> policy
>> 
>> OK, I've created a page a page for the Cataloging Working Group here:
>> 
>> http://open-ils.org/dokuwiki/doku.php?id=cataloging [8]
>> 
>> I added Elaine's bug, and one other just to get the ball rolling.
>> 
>> I don't have time right now to flesh it out or even add all the bugs 
>> I'm subscribed to. I put in a few different categories for types of 
>> bugs, but it's certainly not comprehensive. If you have a wiki 
>> account and the drive to expand the list, by all means, go for it.
>> 
>> If you want a wiki account, send a request to docs at evergreen-ils.org
>> 
>> ---
>> Sarah Childs
>> Technical Services Department Head
>> Hussey-Mayfield Memorial Public Library
>> 250 North Fifth Street
>> Zionsville, IN 46077
>> 317-873-3149 x13330
>> sarahc at zionsville.lib.in.us
>> 
>> On 2013-04-17 15:31, Kent, Alexander D wrote:
>> 
>>> True, it is - to be clear, I'll be keeping track of Authority bugs 
>>> on the wiki. Thanks for catching that!
>>> Alex Kent
>>> Cataloging and Metadata Support and Training Specialist, PALS
>>> Email: alex.kent at mnsu.edu
>>> Phone (work): 507-389-1813
>>> -----Original Message-----
>>> From: evergreen-catalogers-bounces at list.evergreen-ils.org
>>> [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On 
>>> Behalf Of Galen Charlton
>>> Sent: Wednesday, April 17, 2013 2:20 PM
>>> To: Evergreen Community Catalogers
>>> Subject: Re: [Evergreen-catalogers] Bug report -- deposit flag hold 
>>> policy Hi, On Wed, Apr 17, 2013 at 12:09 PM, Kent, Alexander D 
>>> <alexander.kent at mnsu.edu> wrote:
>>> 
>>>> Thank you for sharing, Elaine! I have also posted in on the 
>>>> Authorities wiki page. I will be keeping track of bugs here as 
>>>> well:
>>>> http://evergreen-ils.org/dokuwiki/doku.php?id=authorities [1].
>>> 
>>> But the bug in question is related to hold request policy, not 
>>> authorities.
>>> Regards,
>>> Galen
>>> --
>>> Galen Charlton
>>> Manager of Implementation
>>> Equinox Software, Inc. / The Open Source Experts
>>> email: gmc at esilibrary.com
>>> direct: +1 770-709-5581
>>> cell: +1 404-984-4366
>>> skype: gmcharlt
>>> web: http://www.esilibrary.com/ [2]
>>> Supporting Koha and Evergreen: http://koha-community.org [3] & 
>>> http://evergreen-ils.org [4] 
>>> _______________________________________________
>>> Evergreen-catalogers mailing list
>>> Evergreen-catalogers at list.evergreen-ils.org
>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cat
>>> al
>>> [5]
>>> ogers _______________________________________________
>>> Evergreen-catalogers mailing list
>>> Evergreen-catalogers at list.evergreen-ils.org
>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cat
>>> al
>>> [5]
>>> ogers
>> 
>> _______________________________________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cata
>> loger
>> [9]
>> s
>> _______________________________________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cata
>> logers
>> [10]
> 
> --
> This message has been scanned for viruses and dangerous content and is 
> believed to be clean.
> 
> Links:
> ------
> [1] http://evergreen-ils.org/dokuwiki/doku.php?id=authorities
> [2] http://www.esilibrary.com/
> [3] http://koha-community.org
> [4] http://evergreen-ils.org
> [5]
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> [6] http://www.georgialibraries.org
> [7] http://www.georgialibraries.org/pines
> [8] http://open-ils.org/dokuwiki/doku.php?id=cataloging
> [9]
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> oger
> [10]
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> ogers
> [11] http://www.twitter.com/kmlussier
> [12]
> https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&order
> by=-datecreated&search=Search&field.status%3Alist=NEW&fiel
> d.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.st
> atus%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONS
> E&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_opt
> ion=any&field.assignee=&field.bug_reporter=&field.bug_comm
> enter=&field.subscriber=&field.structural_subscriber=&fiel
> d.tag=acq+&field.tags_combinator=ANY&field.has_cve.used=&f
> ield.omit_dupes.used=&field.omit_dupes=on&field.affects_me.use
> d=&field.has_patch.used=&field.has_branches.used=&field.ha
> s_branches=on&field.has_no_branches.used=&field.has_no_branche
> s=on&field.has_blueprints.used=&field.has_blueprints=on&fi
> eld.has_no_blueprints.used=&field.has_no_blueprints=on
> [13] https://bugs.launchpad.net/evergreen/+bugs?field.tag=authority
> 
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> ogers
_______________________________________________
Evergreen-catalogers mailing list
Evergreen-catalogers at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cataloger
s