Connecting multiple PartKeepr installations to each other would be a very interesting feature.
Possible use cases (I'm using hackerspaces and people as examples, could be companies and subsidiaries or anything similar as well) :
2 hackerspaces in the same city. Both use PartKeepr. It's Sunday. You are working on a projekt in HackerspaceOne, and are missing one single part to finish it. You look in your local PartKeepr installation, and it's not there. But since your local installation is connected to the one in HackerspaceTwo, you can just search their database as well. They have the part, you drive over there quickly, get your part, and can finish your project.
One hackerspace using PartKeepr, and a few members using it as well. You are looking for a part in the hackerspace, and it's not there. But you can see, that one of the members has it in his private collection. You ask them about it, they bring it to the space the next day. You can finish their project.
Possible ways to approach this idea:
The real-time approach
Systems can query each other at any time, using some sort of API. They are authorized by something like OAuth, and can search each others databases. They need to be able to communicate with each other, but with IPv6, this should not be such a big deal.
The synchronization approach
At a given interval, systems interchange data, after an initial synchronization possibly incrementally. This could again be done using a web API, or by exchanging some sort of "dump files", e.g. via email or by uploading them to a public server and fetching them from there. One could go as far as uploading the dump file to a public place, and allow anyone to fetch it, pretty much opening its own database to everyone to query it.
michielbrink
commented
8 years ago
Connecting multiple PartKeepr installations to each other would be a very interesting feature.
Possible use cases (I'm using hackerspaces and people as examples, could be companies and subsidiaries or anything similar as well) :
Possible ways to approach this idea:
Systems can query each other at any time, using some sort of API. They are authorized by something like OAuth, and can search each others databases. They need to be able to communicate with each other, but with IPv6, this should not be such a big deal.
At a given interval, systems interchange data, after an initial synchronization possibly incrementally. This could again be done using a web API, or by exchanging some sort of "dump files", e.g. via email or by uploading them to a public server and fetching them from there. One could go as far as uploading the dump file to a public place, and allow anyone to fetch it, pretty much opening its own database to everyone to query it.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.