The subject search in bibtemplate, interestingly enough, searches
against the keywords index rather than the subject index.
This might just be a fortuitous mistake, but I suspect it is because
the subject index doesn't currently support searches of compound
subjects composed of topic + temporal +
On Thu, 2009-09-17 at 11:49 -0400, Duimovich, George wrote:
Nice to see the MFHD support in 1.6!
I will soon need to demo the MFHD support for our phase II libraries,
and I'd like to confirm what we could anticipate as the the expected
MFHD editing functionality in the first production cut
Yes, it's pretty insane..
Talking to several users of the big 3, I've gotten the sense that if you're a
long time customer - and you don't have many of these add-ons already purchased
from the first contract, then you're on the purchase train every time you need
to do something new. But if
Sorry - forgot to include -- The 404 message I get is:
The requested URL /xul/server/cat/marcedit.xul was not found on this
server.
I guess to save a click or two cataloguers can set the Set bottom
interface as default for OPAC View when batch modifying serials..
George
-Original
Is there a way to have a new brief order record show up as a search result in
the Staff Client search of the catalogue, of course with the appropriate status
e.g. On Order etc.
I've added a new brief record Acquisitions New Brief Record then added
it to a selection list. In the selection
On Thu, 2009-09-17 at 12:20 -0400, Duimovich, George wrote:
Sorry - forgot to include -- The 404 message I get is:
The requested URL /xul/server/cat/marcedit.xul was not found on this
server.
Ah, there needs to be a symbolic link /openils/var/web/xul/server
pointing to
Most of the changes are just to formatting via perltidy, moving towards
standardized 4-space indents.
The substantive changes are:
- $ses-request('open-ils.trigger.event.autocreate', 'renewal',
$self-circ, $self-circ_lib) if $self-is_renewal;
- *1;* added at the end of module,
- SQL
Thanks Dan.
I guess that's a good way to fix a whole bunch of bugs! LOL
MFHD edit works now. Probably more questions later..
George
-Original Message-
From: open-ils-dev-boun...@list.georgialibraries.org
[mailto:open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan
Scott
On Thu, 2009-09-17 at 14:47 -0400, Joe Atzberger wrote:
Most of the changes are just to formatting via perltidy, moving
towards standardized 4-space indents.
I, for one, applaud standardized indents :) Mayhaps you want to add the
vim comment that sets the standardized settings at a file level
Some possible bugs and one enhancement request:
* In Acquisitions Selection Lists (select an item) Edit Order Record... I
get the following error:
FIXME, MARC Editor, loadRecord: TypeError:
grid_rows.getElementsByAttribute(class, marcDatafieldRow)[0] is undefined
* In Selection
On Thu, Sep 17, 2009 at 3:20 PM, Dan Scott d...@coffeecode.net wrote:
Most of the changes are just to formatting via perltidy, moving
towards standardized 4-space indents.
I, for one, applaud standardized indents :) Mayhaps you want to add the
vim comment that sets the standardized
It strikes me that a ticket system would be a more reliable way to track
these bugs. Does anyone else see a problem with putting these in Trac
(maybe getting George an account, if necessary)?
--joe
On Thu, Sep 17, 2009 at 3:41 PM, Duimovich, George
george.duimov...@nrcan-rncan.gc.ca wrote:
Also, some other projects that I've worked on have had a rule (informal
in some cases, more formal in others - hello PHP / PEAR!) that white
space changes should be committed separately from code changes, to make
it simpler for other people to focus on the actual code diffs. I don't
think we
On Thu, 2009-09-17 at 16:22 -0400, Joe Atzberger wrote:
It strikes me that a ticket system would be a more reliable way to
track these bugs. Does anyone else see a problem with putting these
in Trac (maybe getting George an account, if necessary)?
I don't see a problem with this at all, in
On Thu, Sep 17, 2009 at 4:46 PM, Dan Scott d...@coffeecode.net wrote:
On Thu, 2009-09-17 at 16:22 -0400, Joe Atzberger wrote:
It strikes me that a ticket system would be a more reliable way to
track these bugs. Does anyone else see a problem with putting these
in Trac (maybe getting George an
Something that came to mind recently (w/respect to the release process
thread) is that we could set up a Testing/Quality Assurance group of
volunteers who, as one of their powers, would have Trac accounts for
managing bugs like this. Other powers/responsibilities might be vetting
bugs,
We've found some oddities in the times at which items would go from
reshelving to available. I've located a couple issues, and am wondering
what others think about the process.
I've found some items selected by the query that I can't explain. It's
a pretty complex query, but I believe the
From my experience, in 1.6.0.0-rc1 bibs loading fails because trigger
zzz_update_materialized_simple_record_tgr for table real_full_rec
does not exist (is no longer created).
The parallel_pg_loader.pl and pg_loader.pl include statement
SELECT
On Thu, Sep 17, 2009 at 7:33 PM, Bill Ott b...@grpl.org wrote:
We've found some oddities in the times at which items would go from
reshelving to available. I've located a couple issues, and am wondering
what others think about the process.
I've found some items selected by the query that I
On Thu, 2009-09-17 at 16:28 -0400, Jason Etheridge wrote:
Also, some other projects that I've worked on have had a rule (informal
in some cases, more formal in others - hello PHP / PEAR!) that white
space changes should be committed separately from code changes, to make
it simpler for
Mike Rylander wrote:
On Thu, Sep 17, 2009 at 7:33 PM, Bill Ott b...@grpl.org wrote:
We've found some oddities in the times at which items would go from
reshelving to available. I've located a couple issues, and am wondering
what others think about the process.
I've found some items
21 matches
Mail list logo
