Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0 release.
Our library is an independent academic installation, and having recently
celebrated 7 years on Evergreen, a fairly early adopter. I served as release
manager for 2.5 and 2.6, release cycles
+1, support this 100%. Thank you, Galen.
Dan
-Original Message-
From: Open-ils-dev [mailto:open-ils-dev-boun...@list.georgialibraries.org] On
Behalf Of Galen Charlton
Sent: Wednesday, March 02, 2016 10:16 PM
To: Evergreen Development Discussion List
Hello Ken,
Unfortunately, I think your average patron won’t have access through PCRUD even
to their own data. You get empty payloads in PCRUD if you make a requests you
don’t have permission to view.
You can use the user API instead, as it has a method to retrieve the fleshed
user with an
they don't want to feel that burden anymore.
I want more people to feel that burden. It shouldn't just be placed on the
shoulders of our small developer community.
Have a nice weekend everyone!
Kathy
On 03/13/2015 02:32 PM, Dan Wells wrote:
Hello Kathy,
I appreciate the concern expressed here
Hello all,
I've been mucking about in the fine code and getting a bit frustrated, so I'm
looking for input before I move ahead.
As it stands, fine generation is part of the storage API. As such, when it is
called during checkin, it runs in its own transaction (independent of the
circ/copy
Hello Liam,
Thanks for the input. One thing I do want to clarify is that fine generation
even in case #1 would still be functionally independent of the checkin code.
(It has to be, since fine generation for most installations is set to happen
continually, or at least daily.) Plan #1 would
Hello all,
I know that eventually we want to move toward a more fluid DB upgrade model,
but leaving that plan aside for the moment, I'd like to suggest a new policy
for maintenance releases.
My sense is that, as Evergreen matures, people are staying on the previous
version for longer periods,
is greatly appreciated.
Jesse McCarty
City of Burlington
IT Technical Assistant
-Original Message-
From: open-ils-dev-boun...@list.georgialibraries.org
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan Wells
Sent: Wednesday, May 21, 2014 10:50 AM
To: Evergreen Development
...@list.georgialibraries.org
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan Wells
Sent: Tuesday, May 20, 2014 10:56 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4
Hello Jesse,
You want to comment
much appreciated.
Jesse McCarty
City of Burlington
IT Technical Assistant
-Original Message-
From: open-ils-dev-boun...@list.georgialibraries.org
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan Wells
Sent: Wednesday, May 21, 2014 9:27 AM
To: Evergreen Development
Hello Jesse,
You want to comment everything from the failing SELECT
evergreen.upgrade_deps_block_check... up to (but not including) the next
SELECT evergreen.upgrade_deps_block_check You may need to do this several
times before you find them all.
Those checks exist precisely to cause
Hello Bill,
Thanks for the update.
I know others feel differently, but I don’t think we should rule out using
iframes for catalog integration. Iframes are actually pretty close in many
respects to the way the catalog “integrates” into the current (XUL) staff
client. The usual problems with
Struggling with some connectivity issues and lost part of my message. This:
That said, I believe we could rework some bits of the TPAC (and it might not
take much at all) to essentially use
the same templates to dynamically fetch a frameless TPAC “core” for displaying
inline in the staff
Hello Glenn,
Have you checked that ejabberd is actually running? Some subsystems do not (by
default) restart when the system restarts.
On many distros, you can check the status of ejabberd using 'ejabberdctl
status' (run as root or use 'sudo' as appropriate).
What Linux distro are you using?
I'm fine with the decision and consensus, but want to add one thing. I've met
a fair number of users who have a difficult time managing multiple windows in
an ongoing way (call them the closers). We obviously don't have any such
folks responding to this thread, but I think we should be open
Galen, I was deliberately vague in my earlier email, and hope you will
understand if I continue to be :)
I think it is fine to proceed with a separation mindset and see how it turns
out.
Thanks,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
Hello Glenn,
No, Business::ISBN would not be related to the error you are getting. I'd
first try the following command:
osrf_ctl.sh -l -a restart_c
then try running autogen.sh -u once more. If that doesn't work, try and see if
the 'restart_c' command is giving any errors in the logs
Hello Bill,
Thanks for bringing this up! I think this is absolutely the linchpin for
getting the web staff client rolling.
Since this code is still so fresh, it seems ripe for hacking, so I've created a
conference Hackfest page and added this there.
...@list.georgialibraries.org] On Behalf Of Galen
Charlton
Sent: Wednesday, March 05, 2014 2:02 PM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Shared Maintenance Account for Launchpad?
Hi,
On Wed, Mar 5, 2014 at 7:39 AM, Dan Wells d...@calvin.edu wrote:
Here's an idea I
...@masslnc.org
Twitter: http://www.twitter.com/kmlussier
On 3/11/2014 1:26 PM, Dan Wells wrote:
Thanks for +1, Galen.
To help others better evaluate this idea, I've gone ahead and created a new
account and used it for a test run (setting 2.5.3 bugs from 'Fix Committed'
to 'Fix Released
Dan, thanks for adding this. I was curious about this point exactly, since he
states rather bluntly “the bug tracker is a pretty cumbersome place to have a
discussion”, which had me scratching my head a bit.
I’ve always been slightly partial towards forum-like environments since they
have a
Hello all,
Here's an idea I had a while back which I think would make the Launchpad email
system more useful. As it stands, the system sends out an email for every
little change, and, from my perspective, the more meaningful changes sometimes
get lost in the noise. I think we would benefit
Hello all,
I've spent a fair number of hours over the last week getting more familiar with
Bill's prototype code. I still have a *lot* more studying to do before I can
fully appreciate what is happening, but I have at least read through all of the
code involved, and wanted to share a few
Hello all,
Thanks, Dan, for bringing this to the list. It is a better place to have the
discussion, I think. I don’t have a lot to add beyond the original post, but
do wish to clarify a couple of my views.
As far as I know slam dunk criteria has never been formally applied to any
previous
Hello all,
Back at the dev meeting on Nov. 12, I made an offer to continue as RM for an
abbreviated 2.6 release. In the meeting, the discussion concluded with Galen
suggesting that voting the same day as the proposal seems rushed -- I propose
that we give a week, then assent via email if no
Hello,
I can't reproduce this, but here is something you could try which might shed
some light on your problem. First, login using srfsh to get a auth token:
srfsh# login admin YOUR_PASSWORD
Next, use the returned token (the long hex value after Login Session:) to try
running the
Hello all,
I've become a little more familiar with the translation setup, and based on
that limited understanding, I have a concern about how we use translation files
in older versions.
Right now, it seems like our practice is to (occasionally) run update_pofiles
on older branches. However,
Hello all,
Having made the leap from 2.3 to 2.5, we have run into a few issues with the
updated query parser, and rather than dig into something I know from the
surface to be very complex, I am hoping someone might shed some light on what
is going on. The issues I am finding *seem* like bugs,
Hello all,
Now that 2.5.0 is officially out the door, we can turn our attention toward
establishing a release manager for 2.6. At the Hack-a-Way, I took a few
minutes to reflect on how I felt 2.5 had gone, and at one point joked about my
desire to stay on for 2.6. During that talk, and in
Hello all,
The Hack-a-Way is now scheduled for Sept. 17-19. Thank you to everyone for
your patience as we sorted out the details. As I stated before, we will put
out a call for firm commitments later on this summer.
Sincerely,
Dan
--
Hello again,
I apologize for my lack of event juggling skills, but we are being forced to
reconsider the Hack-a-Way dates due to some issues with the facilities. Please
disregard my prior announcement, and expect a final determination early next
week.
Thanks,
Dan
--
Hello all,
Thank you to everyone who replied to the Doodle poll. Based on those results,
the Sept. 24-26 dates have been selected.
Later on this summer we will put out a call for firm commitments, but in the
meantime, if you didn't reply to the poll and think you will attend, please let
me
Hello all,
I wish to offer myself to be the release manager for Evergreen 2.5. Since we
have neither any guidelines nor any history of release manager proposals, I
will try to outline in broad strokes how I would guide the development process.
A release cycle is fairly short, so I think a
Hello Galen,
Thanks for pointing out this thread to me. Since I was personally confused by
#799 showing up in only 2.2 but badly affecting my 2.1 install, I am also
highly in favor of a 2.1.3 release.
Thank you,
Dan
--
Hello Simon,
I think ctx.user.ws_ou() is what you are looking for.
Dan
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 2/15/2013 at 5:27 PM, Mai,
Hello Larry,
Based on what I see here, step 9 was successful. The 'admin'/'open-ils'
credentials are old values which used to be hard-coded into the install, so
your 'egadmin' test is what is relevant here, and it looks fine. I have
updated step 9 of the 'checking_for_errors' page to better
Hello Peter,
This has been on our wish-list for a long time, but at present has not yet made
it onto the do-list. I am interested in collaborating, but given my current
project list, my contribution would likely be confined to a testing/code-review
role.
Dan
--
Hello Hack-A-Way Folks,
I am planning my travel times and budget, and have one question: Does the
subsidized hotel rate apply to the night of Oct. 9 and/or Oct. 13? I would
think 'yes' for the 9th at least, but want to be sure.
Thanks,
Dan
On 8/10/2012 at 11:20 AM,
Hello Olli,
First, I am really glad to see you will be building on Lebbeous's current code.
It's certainly the best public view we have of the managed serials data, and I
would love to see it enhanced to the point that it can integrate more fully
with the summary statement view (something
Hello Martha,
Yes, you will want to add that line between the UPDATE and the first ALTER
TABLE. Since 0706 and 0710 are two versions of the same idea, the upgrade file
probably combines the two (so that is where the line came from). To help
explain what is happening, some of the constraints
Hello all,
Apologies if I missed any prior discussion, but as I am working on implementing
TPAC for my library, I noticed that the 'My Account' link from JSPAC is now
labeled as 'Your Account Log in'. I have no problem with either wording, and
it isn't a huge deal, but I want to make sure we
Hello,
I guess I was too late in filling out the survey, as that is the only slot I
cannot make. Since there aren't any better slots in terms of overall
availability, I don't think there is anything to be done, so this is just an
FYI concerning my absence.
Thanks,
Dan
--
Hello all,
To answer the most immediate questions, I certainly agree that the next version
should be called 2.3 and come out in September.
Beyond that, I think I prefer traditional version numbering over Ubuntu style.
I think Rogan is dead-on with his anxiety comment, but it can also work the
Hello Gayan,
Thank you for your interest in the GSoC Evergreen project. I apologize for not
replying sooner, but our answers are pretty generic at this point, so maybe you
figured things out from other questions being asked.
There is currently one week left in the GSoC application timeline.
Hello Tim,
Cron can be tricky for a number reasons, but one thing which stands out to me
here is the '/usr/bin/perl'. The 'reshelving_complete.srfsh' script is not a
perl script but a SRF Shell script, so we don't need to call the Perl
interpreter in this case. Assuming you can successfully
Hello Vaclav,
Please open a bug for this at https://bugs.launchpad.net/evergreen so that we
can keep better track of this issue.
The attached diff is at least a possible avenue for fixing this problem. I am
not very familiar with this code, but what I have done so far is set the
encoding for
+1
I'm excited.
Dan
On 8/17/2011 at 1:20 PM, Bill Erickson erick...@esilibrary.com wrote:
On Mon, Aug 08, 2011 at 03:02:57PM -0400, Lebbeous Fogle-Weekley wrote:
Bill's merge seems to work well to me. I haven't come across any
features that don't work in this branch. Let's do this!
Hi
Hello Jp,
I think your original message got through, so no need to worry.
As for your problem, I think it is likely that you are running into this bug:
https://bugs.launchpad.net/evergreen/+bug/826844
I hit it myself a few days ago installing 2.0.8. It can effectively prevent
INSERTs into
Hello Jeff,
We do something like this annually (in our case, using LTI for authority
cleanup). I can't say our methods are particularly advanced, but I would be
happy to share what we have done. Are you on 2.0, or an earlier version?
Dan
On 7/27/2011 at 9:57 AM, Jeff Godin jgo...@tadl.org
Hello all,
This email is meant to get the ball rolling again concerning alternate
authentication schemes for Evergreen. What follows is some rough ideas (most
borrowed from the original thread and other software), not a complete plan, so
all input is highly encouraged. The original thread
In a time of drastic change it is the learners who inherit the future. The
learned usually find themselves equipped to live in a world that no longer
exists.
- Eric Hoffer
On Wed, Jul 27, 2011 at 12:11 PM, Dan Wells d...@calvin.edu wrote:
Hello all,
This email is meant to get
Evergreen Users,
In the course of adding various improvements to the Serials module, it was
found that permissions had not been correctly applied to the Serial Control
View interface. This affects Evergreen versions 2.0.0 thru 2.0.6. If you are
using the Serials module in Evergreen 2.0, it is
Hello all,
I spent a few more minutes boiling this down today, and it looks like the
problem is in the OSRF gateway itself. This can be seen very simply by sending
a fake test url to any OSRF gateway which includes the trouble sequence. For
instance: (and note: %25 in the following examples
Hello all,
I have done some experiments and made some interesting findings.
1) to get around the massive error box, we have success with
Tab-Tab-Tab-Space-Tab-Tab-Space :) I think we are checking a box, then hitting
ok, and there may be a simpler way, but that works.
2) This problem persists
Hello all,
We have recently accelerated our timetable to moving to 2.0, and this sudden
immersion is what is causing our recent increase in bug reporting. Yesterday
morning I was exploring a problem with ISSN normalization, and I have spent the
last day trying to understand not only the
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 3/8/2011 at 12:57 PM, Mike Rylander mrylan...@gmail.com wrote:
The drawbacks you mention in both of
I understand that the specific searches will work in any case, but it makes
me more than a little uncomfortable that adding normalizers to a specific
field will silently break searches at the class level. For instance, using
the default config, *any* identifier which contains a '-' but is
Hello Grant,
Dan's solution looks great, but I wanted to add that in 2.0 only there is also
a 'open-ils.circ.copy.due_date.retrieve' method which will get just the due
date and nothing else, which could save on some overhead if you really just
need the date. Let us know if you want to try it
Hello John,
You're example data got me thinking, as in EG the 901 tag is almost always the
last tag, while yours is not. We are still working out the details, but it
seems in fact that a database trigger meant to strip out the 901 is in fact
stripping out all the datafield tags starting at 901.
Hello Mike,
On 2/16/2011 at 12:37 PM, Mike Rylander mrylan...@gmail.com wrote:
On Tue, Feb 15, 2011 at 4:35 PM, Dan Wells d...@calvin.edu wrote:
Hello Mike,
At first glance I think this is a very welcome development, and I have a
just a few comments. First, I would advocate for some kind
Thanks for the feedback. Attached is a patch against trunk with a couple of
changes based on these suggestions.
First, the quote removal code is integrated a little more cleanly and also now
wrapped in a dojo.isOpera condition. Second, the bib.documentElement is now
directly inside the
Hello all,
I spent some time recently trying to get some typical rdetail BibTemplate code
to work in Opera, and made a few discoveries worth sharing. The attached patch
(against the rel_2_0 file, but with no path) is not at all complete code, and
in particular the 'if (1)' lines are just
Hello all,
I have been reluctant to send this message, mostly due to my hope that things
would somehow work themselves out in time, but with 2.0 just around the corner,
I think it would be a mistake to not reach an agreement pre-release on how call
numbers relate to the serials data.
At this
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 1/11/2011 at 12:43 PM, Lebbeous Fogle-Weekley lebbe...@esilibrary.com
wrote:
On Tue, 11 Jan 2011 12:13:15 -0500, Dan Wells d...@calvin.edu wrote:
Hello all,
I have
Hello Mike,
Thanks for weighing in. I think there is overwhelming agreement about *what*
data is needed for a sensible serials display. There is mild disagreement
about how best to store that data for optimal usability. I strongly feel that
an analytic (for lack of a better term, and e.g.
Hello all,
Way back in March I sent a message to the list about adding an auto-barcode
database trigger which didn't get a whole lot of traction, so this is a second,
simpler attempt at the same idea.
To be clear, I am not talking about functionality where we auto-generate *real*
barcodes
Hello again,
This topic was discussed at the IRC developer's meeting today. Here is an
updated version of the function for review:
CREATE OR REPLACE FUNCTION asset.autogenerate_placeholder_barcode ( ) RETURNS
TRIGGER AS $$
BEGIN
IF NEW.barcode LIKE '@@%' THEN
Hello Michael,
I am unsure why some parts of the process are not working for you, but I can
say that our working 949s use the Org Unit short name (e.g. BR1) for both the
owning_lib and circ_lib fields, and also that status and location simply use
the 'name' field (e.g. '3rd floor'). It looks
email - mrpet...@library.in.gov
-Original Message-
From: open-ils-dev-boun...@list.georgialibraries.org
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Thursday, December 09, 2010 12:01 PM
To: Evergreen Development Discussion List
Subject
Hello Mike,
Sorry for my slow reply, things are pretty hectic around here with the Fall
semester starting last week.
Can you describe the purpose of these? Some seem obvious, but some
are not (to me).
I will start with the changes which I think are straightforward. First,
Hello all,
I am hoping the attached changes to the serials schema can make it in before
the alpha2 cutoff (unofficially yesterday-ish). The schema patch is against
trunk, but it should work for any recent branches, and the upgrade file will
need a real upgrade sequence number (currently 'XXX'
:
The attached is a draft of an upgrade script for the serial schema. Please
review before I commit it (along with the corresponding changes to the schema
itself and its install script).
This script is designed to bring the trunk version of the serial schema into
sync with Dan Wells' most recent
Hello Scott,
Despite the fact that some of the other tables have existed for some time now,
AFAIK, only the serial.record_entry table has been used in any stable release
of Evergreen. So I would say it doesn't matter much (the serial.record_entry
table hasn't changed).
Thanks,
Dan
On
Fogle-Weekley 07/15/10 2:15 PM
Aha! My bad for jumping the gun a bit. Looks like it will be cool.
Lebbeous
Dan Wells wrote:
Hello,
There are still some commits forthcoming. The problem you are experiencing
has most to do with the fact that the interface defaults to the 'Items' tab
to spend a couple more days on
the Items tab to get basic predicting/receiving functional again, and will
surely let everyone know when I *think* all the initial pieces are in place.
Thanks,
Dan
On 7/15/2010 at 11:04 AM, Lebbeous Fogle-Weekley lebbe...@esilibrary.com
wrote:
Dan Wells has recently
Hello Alan,
Mostly just a stab in the dark, but maybe this is another form of the Encode.pm
bug mentioned here?:
https://bugs.launchpad.net/evergreen/+bug/525069
In a different post Dan Scott recommends:
Basically, ensure that you have the libencode-perl module installed to
get a working
Hello Scott,
Thanks for moving this forward. I have just one small concern (which I will
immediately drop if I am alone in thinking this). IMHO, the IDL class ids are
a bit on the short side. For instance, in my development code (which I
*really* expect to get out there soon now that things
Hello Mike,
Thanks for the detailed reply. It helps to know we are still not on the same
page :)
First, I want to be clear about what the serial.caption_and_pattern table
actually contains (in my mind). The confusion seems to have been brought about
by my hastily naming a column 'marc' in
Hello again,
pattern_code:
['2','0','a','v.','b','no.','u','12','v','r','c','pt.','u','3','i','(year)',
'j','(month)','k','(day)','w','j']
]
OK, so just an terminology mismatch so far. That's pretty much what I
was thinking too (though we'd want to use JSON in the pattern_code
column,
AM, Scott McKellar m...@swbell.net wrote:
--- On Mon, 5/24/10, Dan Wells d...@calvin.edu wrote:
On 5/24/2010 at 12:25 PM, Scott McKellar
m...@swbell.net
snip
1-3. Sorry for not being more clear, but I think
serial.base (or whatever it is called) will be a direct
replacement
, this is getting longish, so I'm going to stop there and hopefully get the
first reactions I am seeking. Thank you very much for your time and thoughts.
Sincerely,
Dan Wells
--
*
Daniel Wells, Library Programmer
Scott,
Thanks for the reply. See responses below.
On 5/24/2010 at 12:25 PM, Scott McKellar m...@swbell.net wrote:
Questions:
1. What does serial.base look like? For example, will it link to
biblio.record_entry?
2. Using last week's proposed schema as a baseline, how will the new
Hello all,
Attached is a simple patch to fix the bookbag menu not showing up in Craftsman.
This patch is against the 1_6_0 branch. All it does is ID the correct node
for unhiding purposes.
Dan
=
Developer's Certificate of Origin 1.1
By making a
Hello all,
I have committed my MFHD code changes to the new Serials branch for review and
comment from anyone interested. You can see the changeset (with more details)
here: http://svn.open-ils.org/trac/ILS/changeset/16373
At this point I cannot guarantee that the interface is 100% stable,
Hello Bill,
1. I'd recommend keeping the seials-integration [sic] branch up to date
with trunk. It will make the final merge much simpler. I've used svnmerge
[1] in the past with success.
Sounds good, I'll do my best to keep up.
2. I'd like to offer our assistance getting the serials
Hello,
I just did a quick line-by-line comparison with one of our test systems, and
your log was functionally identical to ours up until the point where it ends.
Is that the actual end of the log? If you grep for ERR in the log directory,
do you find anything in any of the other logs? Your
for at least a few weeks
:)
Thanks,
Dan
There's the stuff you put in, but in order to make serials work with
Acq, and make items circulate using the issuance backend that we've
been dreaming of, a ton more will be coming. Dan Wells, expect a lot
of discussion soon on your proposed schema! (
http
Hello all,
This email will explain my library's need for auto-generated barcodes and also
provide our currently deployed patch to accomplish them. We are certainly open
to alternatives for meeting our peculiar needs.
First, concerning the need, as a State and Federal repository, we house tens
Wellsd...@calvin.edu (Dan Wells) wrote:
Hello all,
The attached patch is a very simple means of allowing an option for the
blocking of renews if an item is targeted for a hold. There was some
discussion on IRC about the 'best' way to do this, but other ways (in my
opinion) ended up as just
this additional layer. Ideally any changes made would
augment the current model in an unobtrusive way.
I hope that this message can inspire an interesting and fruitful dialog.
Sincerely,
Dan Wells
* (The term copies is also overloaded in this discussion, as it could mean
the physical manifestation
Hello,
See bug report comments for more information and a patch:
https://bugs.launchpad.net/evergreen/+bug/525950
Dan
On 2/22/2010 at 2:13 PM, Benjamin Shum bs...@biblio.org wrote:
Evergreen version: 1.6.0.2
OpenSRF version: 1.2.2
PostgreSQL version: 8.3.8
Linux distribution: Debian
Hi Mike,
It's a small thing, but any chance of incorporating the fix for
MARC21slim2MODS32.xsl which I posted about on 1/15? I understand if it is
better to evaluate all the changes to the LOC version and incorporate them at
once at a later date.
Thanks,
Dan
--
Thanks for the explanation. Waiting on this is fine with me, I just wanted to
make sure it was missed intentionally.
Dan
On 2/1/2010 at 2:27 PM, Mike Rylander mrylan...@gmail.com wrote:
On Mon, Feb 1, 2010 at 1:49 PM, Dan Wells d...@calvin.edu wrote:
Hi Mike,
It's a small thing, but any
Another minor bug in 1.6 is the lack of a defined 'MERGE_USERS' permission in
the permission.perm_list table (needed for the patron account merging
functionality). I had mentioned it on IRC but not officially reported it
anywhere, so I have now opened a bug for it.
Dan
On 2/1/2010 at 10:57
Resubmit with DCO
=
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
Hello,
I have been doing a lot of experimenting with Vandelay the last few weeks and
have traced many of my failures to one distinct bug. I finally noticed
yesterday why Item Import worked for the 'admin' user but for nobody else. It
turns out there is a bug in one of the database functions
Hello,
Let me start by saying SQL is not my strong suit, and Postgres makes it even
weaker. What I am trying to do is write a single Postgres query/function which
returns all of a user's work_ous and their ancestors without duplicates. I see
that actor.org_unit_ancestors() is there, and
Yes, this appears to be a better solution in all respects.
Thanks Bill.
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 1/18/2010 at 1:07 PM, Bill
Hello,
We were running into a problem with the subject sidebar where part names
were displaying with no space. For instance:
630 00 ‡aBible. ‡pO.T. ‡xCriticism, interpretation, etc., Jewish ‡xHistory
‡y19th century.
diplays as:
BibleO.T
This was traced to an error in the XSL file where the
Hello all,
We have noticed a small bug in the optional automatic voiding of Lost Fees.
The transaction is not marked as finished, as I believe it should be if there
are no other billings (it still shows in the LOST area on the user's account).
I am wondering if more logic will be needed for
1 - 100 of 160 matches
Mail list logo
