Posted by markj on August 21, 2008 at 3:23pm
Jump to:
| Project: | OAI-PMH Module |
| Version: | master |
| Component: | Code |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Any plans to port this module to Drupal 6?
| Project: | OAI-PMH Module |
| Version: | master |
| Component: | Code |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Any plans to port this module to Drupal 6?
Comments
#1
I too would like to see this module for Drupal 6.x
#2
I'll see what I can do, my time is at a premium these days :-(
#3
my time is at a premium these days
Your modules are premium too ;D
Cheers,
-ROR
#4
Ron, I'm going to play with Deadwood to see how well it automates 5-6 migrations. Let me try it with your OAI module and I'll report back.
#5
Interesting module, I wasn't aware of its existence. Unfortunately, while it will likely make a module that works with 6.x, the resultant module will not work with the 6.x version of Biblio :-( because of extensive changes to the database structure. I was reluctant to put to much effort into the OAI module until the database scheme for Biblio 6.x was finalized since they are tightly coupled.
Ron.
P.S. Are you using 6.x of Biblio, or is this a chicken and egg scenario?
#6
Ron, thanks for the heads up on the db structure issue.
We're using Biblio 5 at http://pkp.sfu.ca/biblio but want to migrate to Drupal 6 by end of year.
#7
Hi Mark,
Just to let you know that I have risen from the dead and will likely meet your "end of year" deadline.
Ron.
#8
Subscribing, may be able to offer help if Science Collaboration Framework projects end up needing it. (Very maybe and later...)
benjamin, Agaric Design Collective
#9
OK, it's done... The 6.x version of the OAI2 module is out now.
Ron.
#10
Thanks very much Ron, we'll upgrade to D6 first thing in the new year and set this up.
Mark
#11
You might want to wait for the release version of biblio since there are still a few bugs cropping up in it :-(
#12
Automatically closed -- issue fixed for two weeks with no activity.
#13