New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qiqqa is down since weeks. I need your support extracting or sync my web library. Constant crashes are also an issue. Unable to find any email id of support contact #358
Comments
Hi, I have the same trouble...Did you find a solution? |
Hi , sorry but couldn't find anything till now. Unable to contact anyone from Qiqqa and surprisingly no email or support link provided. It's a loss of almost 4 years work for me. |
Re Qiqqa.com and web libraries: also note the blurb here: https://github.com/jimmejardine/qiqqa-open-source#warning-notice-for-commercial-qiqqa-users-with-a-user-account-and-web-libraries So I guess qiqqa.com (the original commercial Qiqqa site) is finally down 🤔 (Quantisle announced back in 2019 that this would happen somewhere around Q4 2020, so we've had an extra year. But that doesn't help resolve the actual problems. So here's how to approach this:First off, Qiqqa has always kept a local copy of your libraries so my first question for anyone with a library issue is always: Do you still have access to the machine you've been running Qiqqa on? If the answer to that one is If the answer to that is
That being said, I will assume you still have access to your local Qiqqa machine you've been using before.For the risk-averse, it's a two-stage process:
1. create a full backup of the current library collection to ensure nothing can get lost.Re stage 1: all Qiqqa user data is stored in a directory set inside the so-called "Qiqqa base directory": you can find out where that directory is located in your personal machine by following the guide here: https://github.com/jimmejardine/qiqqa-open-source/blob/master/docs-src/Notes/FAQ/How%20to%20locate%20your%20Qiqqa%20Base%20Directory.md Do note that the last bit of that guide addresses so extra work that's irrelevant here, as it was originally written for someone who had a specific issue with one particular library in their Qiqqa library set, so ignore the last couple of paragraphs in there that go on about inspecting the subdirectories and config files, hunting for a specific library. What you need to do instead is BACKUP EVERYTHING in the QIQQA BASE DIRECTORY. (ZIPping it (or using other archival tools) and storing that ZIP archive elsewhere would be a fine idea.) 2. install a new Qiqqa version and have it (auto-)discover your library set.All Qiqqa v8x (v80, v81, v82, v83, ...) releases are binary compatible and can be installed over one another, replacing the existing install. These are also binary compatible with the last Commercial Qiqqa release (v79), so you can safely install an open-source Qiqqa 'over' the current Qiqqa. While Open Source Qiqqa does not support Qiqqa Cloud access, you can still access and use those libraries locally as we can access that local copy that Qiqqa has been using all the time anyway. (The Cloud Access code and keys were never open-sourced by Quantisle, so even if that site were still up, I wouldn't bee able to add that functionality back into Qiqqa again.) TL;DR: open-source Qiqqa doesn't ask for a log-in code, does auto-search and import all existing Qiqqa libraries it can find, including your original Qiqqa Cloud libraries as it will inspect their local copies, which should be up-to-date if the machine you're using now has been the machine you used Commercial Qiqqa on last. (Otherwise your local copy will only carry the material state of affairs at the time of your last Sync action in this local Qiqqa.) For a bit of extra help with installing Qiqqa (and places to get the various releases), see https://github.com/jimmejardine/qiqqa-open-source/blob/master/docs-src/Notes/FAQ/Installing%20Qiqqa%20-%20Updating%20Qiqqa.md Additional, important bit of adviceWhen you're going to install Qiqqa, please use the latest v82 release first, as that is the most stable, generally. The v83 releases are okay for some people, but are all created as test releases for particular problems and have some known bugs, which may bite you. What if I don't like/want v82?If you don't like it at all, then you could opt for the closest possible equivalent of the v79 version, which is v80, the first (and last) OSS release from Quantisle / Jardine -- which is basically v79 with all Cloud Access stripped off plus a couple of quick tweaks to make the beast run without commercial license info & validation.
Let me know how it goes in the comments below. 👍 |
Whoops, forgot to list this link: https://github.com/jimmejardine/qiqqa-open-source#download--install-qiqqa which is a bit more concise on where to find the Qiqqa software releases that aree ready for download and install. |
Thanks @GerHobbelt for such a detailed answer, I really appreciate. But the issue is my Windows crashed and I lost everything on my local machine and no backup at all. I regularly sync my work on my web library and that contains all my 850+ papers / pdfs. It's all my 4 years work. Any how; can I get the access to my web library and download/recover it. I am sorry, was not aware about Qiqqa's exit news. |
Ouch!
The only one who might be able to help you is @jimmejardine himself (Quantisle owner), but I expect your chances to be very slim. This is, regrettably, a fundamental problem with all cloud storage services: when the (commercial) provider goes away/stops for whatever reason -- a management or other involved party action which by definition is outside the control of its users -- you instantly loose access to your data. As far as I know AWS or anyone else does not keep images beyond contract termination date for user access/recovery purposes, hence I believe you'ld be extremely lucky if you'ld get your cloud data recovered. You are in a very bad spot, I'm sorry. 😢 Next part is also for general audience who land here any time later. How about local recovery? Can anything still be pulled off a crashed system/disk?Local recovery chances are also very slim to not-doable, depending on a complex set of circumstances: I'll try & write down the decision tree here:
TL;DR summary?Any chance at recovery requires local direct access to the drive where Qiqqa has been used. Any write activity (implicit or explicit through user action) AFTER THE FACT very quickly lowers your chances at recovery success, even if you're okay with a very much reduced "partial recovery" result. Any non-recoverable (drive) hardware failure means you'll need specialized services. Costly. Any chance at recovery starts with immediately stopping the use of the drive-of-interest. Thus any recovery done by you or other parties that may help starts with: load the drive-of-interest into another machine, where it is not mounted or otherwise directly accessed by any operating system as a regular partition/drive: the only software that may touch it is the (specialized) recovery software. If you immediately stopped using the drive and it's not a non-recoverable hardware failure, then GetDataBack is a pretty good software tool to help you recover your data. I use it semi-regularly for this scenario (no writes after failure, etc.etc.etc. conditions apply). Any other scenario results in steeply increasing costs, depending on circumstances (lots of variables there!) and/or a steeply diminishing chance at recovering part or whole. The key phrase here is "chances are slim to none". Advice to prevent recurrence / Don't let it bite you again
I know. That's extra money and time and effort you could be using more productively elsewhere, or at least that would be my initial thought. Trouble is, I've discovered the hard way that thought is a short-term truth and a very evil long-term lie. Hence I buy extra disks, have collected a couple of (USB) harddrive bays over the years and crashes still happen, but generally loose me (much) less important data than before. |
Hi There, I am in deep trouble. All my research work is on Qiqqa we and I am unable to access as Qiqqa website is down since weeks. I need your support extracting or sync my web library. Constant crashes are also an issue. Unable to find any email id of support contact
The text was updated successfully, but these errors were encountered: