I know exactly what you mean - a lot of the code I’ve developed for our OPAC and is bespoke and tailored for our setup (which is Apache2/mod_perl2/MySQL).

In this case, I think it’s best to simply share the ideas and detail how you went about implementing it. Often times, it can be quicker to write your own version from scratch (using someone else’s ideas) than to try and re-write someone else’s code.

If you do share code, then just remember to provide as much info and comments in the code as possible.

An alternative is make a simpler version of the code available. For example, the code that displays floor plans on our OPAC is quite complex, but I was able to knock together a much simpler JavaScript version that any Dynix customer can add to their OPAC:

http://www.daveyp.com/blog/index.php/archives/4/

Hope that helps!
Dave

I know exactly what you mean - a lot of the code I’ve developed for our OPAC and is bespoke and tailored for our setup (which is Apache2/mod_perl2/MySQL).

In this case, I think it’s best to simply share the ideas and detail how you went about implementing it. Often times, it can be quicker to write your own version from scratch (using someone else’s ideas) than to try and re-write someone else’s code.

If you do share code, then just remember to provide as much info and comments in the code as possible.

An alternative is make a simpler version of the code available. For example, the code that displays floor plans on our OPAC is quite complex, but I was able to knock together a much simpler JavaScript version that any Dynix customer can add to their OPAC:

http://www.daveyp.com/blog/index.php/archives/4/

Hope that helps!
Dave