Chris,
Many thanks - picking up on you points below:
At 09:57 AM 1/7/2012 +1300, Chris Cormack wrote:
I have successfully use that script to link authorities to biblio records
after doing a migration. But the way it works is to remove all links and
recreate.
Not sure about the "recreate" bi
I have successfully use that script to link authorities to biblio records
after doing a migration. But the way it works is to remove all links and
recreate.
Course I didn't do this on a server people were using, which it sounds like
you are, to have lost 100 biblios.
Its included for that use cas
Paul,
Bug 5683 is a different problem. It results in your records being
unrecoverably corrupted. You'd recognize the problem by the fact that after
running link_bibs_to_authorities.pl you wouldn't be able to look at some
records in your catalog. What you are encountering is the
apparently-intended
Paul,
The link_bibs_to_authorities.pl script is hardcoded to ALWAYS erase manual
links. I'm not sure what the reasoning is behind that. But, every time
you run it, any link you've done manually that the script can't
automatically figure out will be removed. Nature of the beast (for now, at
lea
Im assuming you did this on your testing/staging server right?
Id restore that from backup, then try applying the patch and see if you get
better behaviour.
If so, then do it on your production machine.
Chris
On 7 Jan 2012 08:47, "Paul" wrote:
> Bug 5683 (link_bibs_to_authorities.pl can corrupt
Bug 5683 (link_bibs_to_authorities.pl can corrupt records) was signed off
some months ago, but is perhaps a little too cryptic for me to follow in
detail. Can someone help? As far as I can see, without remedial action,
this is catastrophic.
Following difficulties we have had migrating 3.2 to
Given the immediate and positive response to this proposal, I've gone ahead
and started implementing it. I've created the new Status fields, but
they're currently invisible. Once they're placed into the Workflow,
they'll appear.
I'd like to schedule adding them to the workflow, modifying the can
> What do people think? Does this sound like a reasonable change to make?
+1
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git
Le 06/01/2012 15:37, Ian Walls a écrit :
What do people think? Does this sound like a reasonable change to
make? Any objections?
+1
--
Julian Maurice
BibLibre
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-commu
> What do people think? Does this sound like a reasonable change to make?
+1
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.o
2012/1/6 Ian Walls :
> What do people think? Does this sound like a reasonable change to make?
+1
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.ko
+1 --gmc
On 01/06/2012 09:37 AM, Ian Walls wrote:
Fellow Koha-ckers,
A comment on bug 7167
(http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167) has
gotten my interest re-awakened about a proposed Bugzilla revision that
had been floated earlier this release cycle.
I'd like to remove
Le 06/01/2012 15:37, Ian Walls a écrit :
> Fellow Koha-ckers,
> I'd like to remove Patch Status, and move all those values to the
> regular Status field. This has the following advantages:
>
> * Status is a built-in field, so it's got much richer support in
> Bugzilla. For example, status
+1
On Fri, Jan 6, 2012 at 9:40 AM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> +1 here.
>
> 2012/1/6 Ian Walls :
> > Fellow Koha-ckers,
> >
> >
> > A comment on bug 7167
> > (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167) has
> gotten
> > my interest re-awakened abo
+1 here.
2012/1/6 Ian Walls :
> Fellow Koha-ckers,
>
>
> A comment on bug 7167
> (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167) has gotten
> my interest re-awakened about a proposed Bugzilla revision that had been
> floated earlier this release cycle.
>
> I'd like to remove Patch
Fellow Koha-ckers,
A comment on bug 7167 (
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167) has gotten
my interest re-awakened about a proposed Bugzilla revision that had been
floated earlier this release cycle.
I'd like to remove Patch Status, and move all those values to the regu
Hello,
a very important information: After a long discussion with chris_c and
chris_n, it seems I made a mistake and have found a hidden problem.
* the hidden problem (that was hidden for me, and probably for most of
you. both chris where aware) :
in 3.4 and 3.6, when a patch with a updatedatabas
17 matches
Mail list logo
