Need help with qiqqa-open-source?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

jimmejardine
180 Stars 29 Forks GNU General Public License v3.0 1.2K Commits 161 Opened issues

#### Description

The open-sourced version of the award-winning Qiqqa research management tool for Windows

!
?

# 18,472
JavaScr...
npm
mathjax
WPF
1094 commits
# 592,464
transla...
Shell
c-sharp
TeX
39 commits
# 3,157
imagema...
sass-fr...
splash
pipelin...
1 commit

# Qiqqa (Open Source)

Now open source award-winning Qiqqa research management tool for Windows.

This version includes every feature available in Commercial Qiqqa, including Premium and Premium+.

Unfortunately we have had to remove the web cloud sync ability as that involves storage costs. Users are encouraged to migrate their Web Libraries into Intranet libraries, and use Google Drive or Dropbox as the 'sync point' for those libraries.

New Qiqqa (pre)releases are available at this link: https://github.com/GerHobbelt/qiqqa-open-source/releases -- scroll down a bit and click on 'Assets' to twirl open the download list for each released version and download the setup exe there.

It's a Windows setup executable, which can be installed over your existing Qiqqa install as usual by following the installer prompts.

For release notes see CHANGELOG.

### What about these different releases? Which one should I use?

See the notes here. If you feel unsure about it all, then the conversation at #282Which version should I be installing as I move from "old Qiqqa" to open source? might be useful for you as well.

### Need help?

To be notified of new releases subscribe to the Google Group 'qiqqa-releases'.

### Just in case

On the unhappy chance where you want to revert to a previous Qiqqa version, these are all available for download at https://github.com/GerHobbelt/qiqqa-open-source/releases (v82 and v81 prereleases) and https://github.com/jimmejardine/qiqqa-open-source/releases (v80 release).

All v82, v81, v80 and (commercial) v79  Qiqqa releases are binary compatible: they use the same database and directory structures, so you can install any of them over the existing Qiqqa install without damaging your Qiqqa libraries.

Enjoy Qiqqa and take care!

### Miscellaneous Notes

• DO NOTE that the v82 releases are prereleases, some of which are only lightly tested and may include bugs. Backup your library before testing these, even if you like living on the edge...

@GerHobbelt has joined the team and keeps the bleeding edge rolling. For recent changes see closed bugs list.

• Qiqqa Commercial software installer releases v66 to v79 are available at qiqqa.com at least until 2020 and also here.

## Documentation For Users

Documentation still needs a lot of work. All help is appreciated. The Commercial Qiqqa manual is available at qiqqa.org.

Other documentation material is being added as we go; the sources for that are available in this repository's docs directory.

## Qiqqa Collaborators & Developers Wanted

### For Developers: Building Qiqqa From Source

It needs some technical experience. See the DEVELOPER-INFO for details.

# WARNING NOTICE for Commercial Qiqqa users with a user account and Web Libraries

## 🆘 ❓ I previously used v79 with one or more libraries. I also have a web account.

Note this from the qiqqa.com commercial website (emphasis mine):

After 10 years of your support we have decided to make Qiqqa open source so that it can be grown and extended by its community of thousands of active users.

NB: We will be discontinuing Web Library support for Qiqqa at the end of 2020. So you’ll have one year within which to install the latest version of Open Source Qiqqa (which is improving daily), migrate your Web Libraries into Intranet Libraries, and enjoy all the Premium and Premium+ features of Qiqqa for free (except Web Libraries)!

## Web Libraries (Commercial Qiqqa cloud storage) will be discontinued 'at the end of 2020'.

The only way to access your REMOTE = CLOUD-STORED libraries is by using Qiqqa v79, as the Cloud access code was never open sourced.

The way that Open Source Qiqqa (v80 and later) appear to access your Web Libraries is by discovering the local copies of those libraries, which Commercial Qiqqa (v79 and older) kept (manually) synchronized. That way, Qiqqa continues to provide access to your former Web Libraries. (See also #4.)

Therefore, if you doubt or know your local copy of your Web Library to be out of sync with your cloud-based Web Library (because you or others updated/synced that cloud-based library from other machines after your last sync action on this one) you MUST install Commercial Qiqqa v79 (available here among other places) to log into your Qiqqa cloud account, synchronize your Web Libraries with your local copy and then re-install Qiqqa Open Source (v82 preferentially).

Qiqqa versions v79, v80 and v82 can be installed over one another without issue as they are binary compatible re Qiqqa local library files, so there's no expected harm done in installing v79 over v82, particularly if you limit your activity to syncing Web Libraries.

(By the way: the

setup.exe
will certainly yak about you installing Qiqqa over a 'newer' version. Disregard and continue.)

Then, once you re-installed v82, it will discover your local Web Library copy again (now synchronized) and you should be good to go.

Do note that the name of the library as shown in v82 might be UUID-like gobbledigook instead of the proper title you gave it back in the day of Commercial Qiqqa and v79. The contents should be available untrammeled though.

## 🆘 ❓ Got a question?

Ask your question on github at https://github.com/jimmejardine/qiqqa-open-source/issues by "filing an issue": there's nothing to it, just click the green "New Issue" button at the top-right corner there. 😄

While Google might still list search hits pointing at a Qiqqa forum at getsatisfaction.com, that one is defunct since Q2 2020.

No matter, you can ask your questions in the "issue tracker" mentioned above; creating a github account is easy and free.

### Tip: you can also search the issue tracker to see if someone already asked the same question.

When you find an issue which addresses your problem, see if the discussion there is a sufficient answer. When it is not and the issue is flagged as closed, please file an NEW issue. You may mention the existing issue by pasting a link to it in your text (or for github-savvy folks: enter the issue number prefixed with a hash, e.g.

#284
; github issue preview would show that one as: #284).

## 🆘 ❓ After several years I returned to research; I have an older Qiqqa library which I would like restored. Can you help?

(Very) probably we can.

While folks have emailed me (GerHobbelt) directly, the more prudent approach would be to file an issue as mentioned in the 'Need help?' section further above as email may easily inadvertedly get lost or regrettably go unread and 'disappear' in the torrent of email I receive daily. GitHub issues are here and will stay here, enabling me (and others) to respond when we have time. Issues do not disappear in an overflowing bucket.

I'm not discouraging you from emailing me, but rather suggesting that there may be two ways about this rather than only one: you could email me and file an issue requesting help!

Of course, email conversations are a tad more private, so that's up to you to decide. In the EU we now have a law giving us "the right to be forgotten on the Internet" but frankly, I'm not counting on it and never have assumed as much since the day I encountered "writing" and computers 40+ years ago. Your data is perhaps perishable at the most inconvenient of times, but when you want it to be vamoosed, you can bet your bottom it's clinging to a wall some place. 😉
The point being? It's up to you to consider and decide on the amount and level of privacy of your Qiqqa data and act and communicate accordingly at all times.