<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi all,<br>
<br>
This is great! I think it will benefit everyone if the cataloging
bugs (and bugs for other functional areas) are easier to track.<br>
<br>
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.<br>
<br>
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):<br>
<br>
<a
href="https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=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.tag=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_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on">https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-datecreate
d&s
earch=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=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.tag=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_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on</a><br>
<br>
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 <a
href="https://bugs.launchpad.net/evergreen/+bugs?field.tag=authority">https://bugs.launchpad.net/evergreen/+bugs?field.tag=authority.</a><br>
<br>
I just thought it might help streamline the process of tracking
these bugs.<br>
<br>
Kathy<br>
<pre class="moz-signature" cols="72">Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
<a class="moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>
Twitter: <a class="moz-txt-link-freetext" href="http://www.twitter.com/kmlussier">http://www.twitter.com/kmlussier</a>
</pre>
On 4/17/2013 8:00 PM, Hardy, Elaine wrote:<br>
</div>
<blockquote
cite="mid:9970c319.000011b8.00000008@GPLS-EHardy-LatitudeE6420.pls-hq.org"
type="cite">
<pre wrap="">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
<a class="moz-txt-link-abbreviated" href="mailto:ehardy@georgialibraries.org">ehardy@georgialibraries.org</a>
<a class="moz-txt-link-abbreviated" href="http://www.georgialibraries.org">www.georgialibraries.org</a>
<a class="moz-txt-link-abbreviated" href="http://www.georgialibraries.org/pines">www.georgialibraries.org/pines</a>
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org">evergreen-catalogers-bounces@list.evergreen-ils.org</a>
[<a class="moz-txt-link-freetext" href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org">mailto:evergreen-catalogers-bounces@list.evergreen-ils.org</a>] On Behalf Of
Sarah Childs
Sent: Wednesday, April 17, 2013 4:25 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:evergreen-catalogers@list.evergreen-ils.org">evergreen-catalogers@list.evergreen-ils.org</a>
Subject: Re: [Evergreen-catalogers] Bug report -- deposit flag hold policy
OK, I've created a page a page for the Cataloging Working Group here:
<a class="moz-txt-link-freetext" href="http://open-ils.org/dokuwiki/doku.php?id=cataloging">http://open-ils.org/dokuwiki/doku.php?id=cataloging</a>
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 <a class="moz-txt-link-abbreviated" href="mailto:docs@evergreen-ils.org">docs@evergreen-ils.org</a>
---
Sarah Childs
Technical Services Department Head
Hussey-Mayfield Memorial Public Library
250 North Fifth Street
Zionsville, IN 46077
317-873-3149 x13330
<a class="moz-txt-link-abbreviated" href="mailto:sarahc@zionsville.lib.in.us">sarahc@zionsville.lib.in.us</a>
On 2013-04-17 15:31, Kent, Alexander D wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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: <a class="moz-txt-link-abbreviated" href="mailto:alex.kent@mnsu.edu">alex.kent@mnsu.edu</a>
Phone (work): 507-389-1813
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org">evergreen-catalogers-bounces@list.evergreen-ils.org</a>
[<a class="moz-txt-link-freetext" href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org">mailto:evergreen-catalogers-bounces@list.evergreen-ils.org</a>] 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
<a class="moz-txt-link-rfc2396E" href="mailto:alexander.kent@mnsu.edu"><alexander.kent@mnsu.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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:
<a class="moz-txt-link-freetext" href="http://evergreen-ils.org/dokuwiki/doku.php?id=authorities">http://evergreen-ils.org/dokuwiki/doku.php?id=authorities</a>.
</pre>
</blockquote>
<pre wrap="">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: <a class="moz-txt-link-abbreviated" href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a>
direct: +1 770-709-5581
cell: +1 404-984-4366
skype: gmcharlt
web: <a class="moz-txt-link-freetext" href="http://www.esilibrary.com/">http://www.esilibrary.com/</a>
Supporting Koha and Evergreen: <a class="moz-txt-link-freetext" href="http://koha-community.org">http://koha-community.org</a> &
<a class="moz-txt-link-freetext" href="http://evergreen-ils.org">http://evergreen-ils.org</a>
_______________________________________________
Evergreen-catalogers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal</a>
ogers _______________________________________________
Evergreen-catalogers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal</a>
ogers
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Evergreen-catalogers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cataloger">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cataloger</a>
s
_______________________________________________
Evergreen-catalogers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a>
</pre>
</blockquote>
<br>
</body>
</html>