Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
Is there any plan for porting this module to D8??
Thanks
Hello,
Is there any plan for porting this module to D8??
Thanks
Comments
Comment #1
Bwolf CreditAttribution: Bwolf commentedI would also like to know if there will be a port to Drupal 8.
Great module!
Comment #2
Bwolf CreditAttribution: Bwolf commentedI would also like to know if there will be a port to Drupal 8.
Great module!
Comment #3
azin CreditAttribution: azin commentedAnd will it use FieldAPI?
Comment #4
rjerome CreditAttribution: rjerome commentedIt's not impossible, but it may require some crowd funding or other sponsorship...
Comment #5
azin CreditAttribution: azin commented@rjerome, approximately, how much do you need?
Comment #6
alancsilver CreditAttribution: alancsilver commented@jerome, I am sure there are a lot of us that rely on this module and would be happy to help the cause to get this into D8
Comment #7
Bwolf CreditAttribution: Bwolf commentedHow can we help contribute?
Comment #8
tenken CreditAttribution: tenken as a volunteer commented@rjerome Would something initiated by the Drupal community via https://www.drupalfund.us/ work for you. Could you provide a rough cost/time estimate.
The Drupal 8 Rules module initially used this as a funding model.
Comment #9
azin CreditAttribution: azin commented@rjerome, a cost/time estimate would be rather good to have at this point
Comment #10
rreck CreditAttribution: rreck commentedI wish this was being ported to D8 too.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedYeah Biblio is crucial for many. This will need crowd funding.
Comment #12
amberparker24 CreditAttribution: amberparker24 commentedAnother vote for D8 port. Following for contrib/funding update
Comment #13
pbattino CreditAttribution: pbattino commentedI'm in the same both: just moved an old library to Biblio, and it's the only major module in our site that has no D8 version in sight.
So when time comes (not urgent right now but it will be urgent down the line) I will have to find a solution and I really hope I can contribute to the migration, like ring-fencing some time of one of our developers to do just that.
Comment #14
Bwolf CreditAttribution: Bwolf commentedHow can we contribute to funding?
Comment #15
keha3912 CreditAttribution: keha3912 commentedsub
Comment #16
guignonv CreditAttribution: guignonv as a volunteer commentedsubscribing. We have several sites using the biblio module which is an awesome piece of work. We definitely need it for Drupal 8.
Comment #17
rcodina CreditAttribution: rcodina commented+1 for porting Biblio to D8.
Comment #18
alevin CreditAttribution: alevin commented+1
Comment #19
Zythyr CreditAttribution: Zythyr commented+1
Comment #20
Erik Seifert CreditAttribution: Erik Seifert commentedWe have a payed work for a initial biblio module in drupal 8. It will be started in next weeks. We will create a github project and post the link here.
Comment #21
hopfrog CreditAttribution: hopfrog commentedWOW Eric. Thanks
Comment #22
Bwolf CreditAttribution: Bwolf commentedThis is great!
Comment #23
TokiGreat news for a great module.
Comment #24
ar-jan CreditAttribution: ar-jan as a volunteer commentedGood news. What version will it be based on (1.x or 3.x)?
Comment #25
Erik Seifert CreditAttribution: Erik Seifert commentedFirst we meet up with the institute and create a concept. Second we check current versions. Then create a technical concept. Everybody is invited to help how we solve the different kinds of requirements for this module. (Think we make Wiki Pages and issues on Github)
Here will be the github repository.
https://github.com/b-connect/biblio
Comment #26
Erik Seifert CreditAttribution: Erik Seifert commented@ar-jan
I think version 3 looks more suitable for entities as version 1.
Comment #27
dhansen CreditAttribution: dhansen as a volunteer commentedVery excited about a Drupal 8 version!
Super curious about potential roadmaps. Biblio has for a very long time been a module that has almost fit my needs and those of my clients, but not quite. Usually I have to build out some additional tools or integrations to get precisely what I want. I am hoping for something a little more extensible in D8.
Ideally, I'd like to see some core Biblio functionality broken out into a 'Citation API'. The API would provide the core Biblio content type turned into an entity, and then the different publication types within Biblio would become bundles for that citation entity type. This would better map Biblio's configuration to existing Drupal structures. The Biblio module then would for the most part become a view with a collection of settings and maybe integrations, making it much more lightweight. If we wanted we would even turn things like Styling into separate modules, meaning APA or MLA formatting could be enabled as needed on citations.
I've not experimented much with the 3.0 version, though I know it is a bit more entity-focused. Maybe some of that is already in place there, but I'm still very excited to see what direction Biblio is taking for D8.
Comment #28
Erik Seifert CreditAttribution: Erik Seifert commentedThat's the plan ;-) biblio and authors are entities with bundle support. Styles should be pluggable through a style provider plugin system (citationstyles.org will be implemented).
We need a mapping for drupal fields to biblio fields. We need zotero support, so we add a plugin for the drupal rest api and a feeds importer plugin.
The goal is to use as much drupal base functionality as possible.
Comment #29
rjerome CreditAttribution: rjerome commented@Erik Seifert
I'm more than a little surprised that your plan...
...doesn't start with talking to the current maintainer of the Biblio module.
I have been the maintainer for 10 years, and while I applaud your enthusiasm, you are the at least the second (maybe third) person who has come along with big plans to change everything. To date, none have had the staying power to actually create and maintain a production worthy product (witness Biblio versions 7.2 & 7.3), so I think one of the really important questions that Biblio users should be asking is are you willing to commit to long term maintenance of the module?
In addition to being the author of version 4.x, 5.x, 6.x and 7.x of the Biblio module, I am also the author of the PHP version of the CiteProc code on citationstyles.org, so it seems to me that I might have something to add to the conversation.
While I know that I have not been present in this forum as much as I used to be, I am still the maintainer of this module.
Ron.
Comment #30
Erik Seifert CreditAttribution: Erik Seifert commentedWe need to implement this functionaility this year. It seems not to be started something for drupal 8 in the last 7 months. If you want to support this work it would be nice. But if not we will start a new project.We have now the money and the resources,
Sorry about this harsh words. I have also some long running orojects on drupal.org build with my heart blood.
Comment #31
ar-jan CreditAttribution: ar-jan as a volunteer commentedI can see Ron's point. Ideally (from my perspective as a long-term site-builder and Biblio user) a Drupal 8 port would end up on drupal.org, be supported and maintained there, and have a migration path from 7.x-1.x. For that to happen, planning/discussion/collaboration with the current maintainer would be a natural first step, I think.
I hope you'll be trying to work this out, Erik and Ron. It would be a shame to see efforts in this space be divided over different modules.
Comment #32
pbattino CreditAttribution: pbattino commentedI agree with ar-jan: I really hope there's not yet another forking and Erik and Ron can work together.
Ron, I understand your frustration and it's good that you remind us of the unfortunate case of Biblio versions 7.2 & 7.3. However I don't understand why you haven't contributed to this conversation before, not just now to tell Ron "I'm surprised you did not talk to me first".
Well... we are ALL talking to you first! We are here in this forum for this reason, this ticket has been opened for more than a year and the only comment for you was "it's not impossible". Erik said he found the resource, what else should he say? He was perhaps harsh, but he highlighted the whole point of open source software: there are no walled garden, if somebody does not bring a project forward, somebody else will do it, with or without fork (hopefully without), not even the maintainer can stop that.
So, Erik's needs and intentions are clear. Also, the needs of many other Biblio users are clear: soon or late we will NEED to migrate to D8 (and no, it's not necessarily a matter of "big plans to change everything": it's porting to D8 as simple as that).
What about your intentions?
Comment #33
Erik Seifert CreditAttribution: Erik Seifert commentedHey @rjerome ,
so we should start a discussion how we start a drupal 8 version ?
We have a initial plan https://github.com/b-connect/biblio/wiki . Do you think that could be a good start ? This plan is also designed for our affords of a initial version.
Comment #34
johnkennedy CreditAttribution: johnkennedy commentedErik, There doesn't seem to be anything here:
https://github.com/b-connect/biblio
Has any work been done on a port?
Ron, Have you had any more support around this? Have you had any funding that might allow you to create a D8 port?
There are a significant number of Higher Ed orgs waiting on this module and if there are no plans it would be great to at least get all of the stakeholders into a meeting to determine needs vs effort.
Comment #35
Erik Seifert CreditAttribution: Erik Seifert commentedHello,
There are some ideas on the wiki page. Also i start a proof-of-concept branch. We are waiting for a order from our customer to start a initial module. At this time there is only planning and collecting ideas.
Comment #36
Bwolf CreditAttribution: Bwolf commentedHi All
Thanks for moving the project forward. Just checking the status.
Comment #37
Bwolf CreditAttribution: Bwolf commentedLet us know if you need people to help test during the development phase.
Comment #38
usdv CreditAttribution: usdv commentedHello,
There is a separate project for drupal 8 that provides almost the same features: https://www.drupal.org/project/bibcite
There is no release yet, but it's under active development process.
Comment #39
Bwolf CreditAttribution: Bwolf commentedWill Pubmed IDs be supported?
Comment #40
Bwolf CreditAttribution: Bwolf commentedusdv,
Are you working with rjerome and Erik Seifert?
It would be great to see a combined effort.
Comment #41
Ed Carlevale CreditAttribution: Ed Carlevale as a volunteer commented@ErikSeifert @rjerome. I wholly support Ron's frustration here but also want to find the most efficient way to get a Drupal 8 version of the Biblio module up and running. Drupal's dominance in academic web development would be unthinkable without the work he has contributed over ten years as the developer and maintainer of the Biblio module. And he is right to ask about the longterm commitment of new developers. That is absolutely critical. The Biblio module is not like any other Drupal module. Maintaining it over the longterm requires both commitment and unique skills that go beyond the usual solid developer skills.
To my mind, Harvard did a tremendous disservice to the Biblio module. They forked the 7.1 version to create the 7.3 version -- as far as I can tell, simply because they needed to customize it for Open Scholar. And then, like the rest of Open Scholar, Harvard contributed nothing back to the Drupal ecosystem. That was a devastating one-two punch. And the result, besides hurt feelings and inadequate development, is showing up in this confused discussion of how best to port the Biblio module from Drupal 7 to Drupal 8.
To move forward, let’s try to keep feature requests off this thread and simply focus on a discussion of how best to get a Drupal 8 version of the Biblio module.
These are the major players right now, as I see it:
The piece that I will help coordinate is going after funding to support development. So many universities and government agencies rely on the Biblio module, and all of them will be stopped dead in their tracks without a Drupal 8 release.
Ron’s last release was on 2016-Apr-08 (7.x-1.x-dev tar.gz). Clearly he is still maintaining the module, so for courtesy, respect, and practical reasons, our efforts should go to supporting his lead. These Drupal.org comment threads are incredibly unhelpful for the kind of discussion we are trying to have here, and miscommunication and hurt feelings are practically built into the process. I’ve been trying to untangle where things stand with the Biblio module for the past week, and only my absolutely need to get a Drupal 8 version up and running forced me to read through everything. And more than likely, I’ve missed some very important pieces of the discussion.
To sum up the scenario I’m trying to push:
Ed Carlevale
MIT Drupal Group
Comment #42
guignonv CreditAttribution: guignonv as a volunteer commentedI 100% agree with #41. If this helps, if you need a letter of support to raise funds, I can manage to have one signed by several French public institutions and a CGIAR center for instance. Just let us know...
We _need_ it.
Comment #43
Bwolf CreditAttribution: Bwolf commentedHi All
I led a table discussion and the Higher Ed Summit at DrupalCon in New Orleans about this issue.
“Identifying and Supporting Modules Important to the Academic Community”
1) Identify modules important to the academic community.
2) Figure out how institutions can support. i.e. module support campaigns, developer time etc.
3) Look at a funding model where universities and institutions can easily contribute. Right now there is not a easy way to do this.
Let’s set up a group page to continue the discussion.
Comment #44
Bwolf CreditAttribution: Bwolf commentedI set up a group page
https://groups.drupal.org/education-module-funding
Comment #45
kruhak CreditAttribution: kruhak at ADCI Solutions commentedHello. I want to say a few words about "Bibliography & Citation" module.
There is only dev release available for now, with possible breaking changes in a few places. So module is under active development and we're focused now on making stable and flexible core functionality. We are planing to make a scalable structure based on Drupal entity system. After this part is done we'll be able to easily extend module by additional features considering a lot of hidden obstacles under the hood of the Biblio module.
We are interested in the long-term development and supporting of this module.
Part of the planing functionality is already implemented. You can find list of currently implemented features, read information about our plans and download latest dev release on the project's page.
We are absolutely open for cooperation with the community and will be glad of any help.
As a developer, I agree that we need a place for open dialogue. I think that group on the drupal.org will be a good decision.
“ADCI Solutions”, developers of the “Bibliography & Citation” project.
Comment #46
marqpdx CreditAttribution: marqpdx as a volunteer commentedhi All,
First want to thank the current biblio module coders, implementers and maintainers, especially the core developers. Amazing module!
I hope we can marshall collective experience to move our shared goals forward, that of having a very solid Bibliography module for Drupal 8.
I would like to second the recommendation to look at the "Bibliography & Citation" module; i just installed it on my new D8 site, and successfully imported a bibtex file. That made me happy. It worked well.
If Ron or Erik or Gizra or any other skills Drupal folks could look at that module, and see if it is a useful starting point, we might get some momentum.
It would be a huge effort to port to D8, and perhaps starting from a new codebase with existing knowledge would give us the best traction.
Just some thoughts
m
Comment #47
agerard CreditAttribution: agerard commentedDitto #46, #41, #32. I'm about to embark on a new site design for my (education sector) employer, to replace an antiquated citation database/java user interface tool, and was hoping to jump to Drupal 8 with a biblio module rather than recreating it all by messily importing to custom content type with views output. I've taken a lot from the community and have contributed very little - I'd be really happy to have the opportunity for testing, input, even code contribution (slowly growing php skills...) but it seems first the key players need to be willing to get together. I hope that will happen!
Comment #48
gunwald CreditAttribution: gunwald commentedIs there any hope for any progress on the Drupal 8 port?
Comment #49
neoxavier CreditAttribution: neoxavier commentedI think the best bet at the moment is to use the following module
https://www.drupal.org/project/bibcite
and migrate the data using the following module (if you want to upgrade your websites)
https://www.drupal.org/project/bibcite_migrate
Comment #50
Bwolf CreditAttribution: Bwolf commentedI have been testing Bibcite for my Drupal 8 lab project framework. The developer has done a great job to move the project forward responding to questions in the issue queue and implementing features.
Comment #51
Alan D. CreditAttribution: Alan D. commentedAny updates / thoughts from the maintainers on this?
I was contacted recently about some external devel's considering putting some effort into the 7.x branch albeit I can't see any activity from that, but talk regarding the 8.x seems to be quiet.
bibcite looks like it could be a useful start, but it does treat citations as a separate entity, which is both good and bad.
Comment #52
antongp CreditAttribution: antongp at ADCI Solutions commentedAlan D., what exactly you consider as bad things regarding separate entities?
Comment #53
Alan D. CreditAttribution: Alan D. commentedSometimes entries are effectively just content like any other post on a site ;)
Really only matters when you start doing mixed views or entity.query services, even for something as simple as recent content.
[edit]
And stating the obvious, node specific add-ons: content moderation...
Comment #54
Liam MorlandThe solution to this is to use bibcite and bibcite_migrate.