search

hbons / SparkleShare

Share and collaborate by syncing with any Git repository instantly. Linux, macOS, and Windows.
https://sparkleshare.org
Other
4.88k stars 576 forks source link

filter notifications #401

Closed robinboast closed 12 years ago

robinboast commented 12 years ago

Hi SparkleShare. I have just been looking at SparkleShare only recently as a way of solving some rather serious problems in eHumanities, eScience and digital repository access. This all sounds very grand for a file sharing platform, but the problem that we have in all these areas is that to share information between diverse, very diverse, user groups, requires either hyper-limiting metadata or some sort of portal. We have been looking at PubSubHubBub, but have found that wanting as the content is too limited. SparkleShare seems ideal for what we are looking for, but for one problem. Clients in our networks need to be able to idiosyncratically filter the notifications and even what files get synced as there is a lot of data. Have you considered implementing simple client side filtering? Please do as this would overcome some huge limitations for specialist data sharing networks. Happy to talk more about this if you are interested.

hbons commented 12 years ago

You can have different folders for different things? We can't do filtering on the file level because of how git works. Also not getting some things to some people defeats the purpose of the project a bit. :)

robinboast commented 12 years ago

Thanks Hylke, and that would be fine if some sort of facetted classification was sufficient. I understand that the target users would want to sync all content, but I think there is a whole other user group that you are not considering here. Researchers, institutions and even casual parties have such diverse interests and would like to share content. However, the other users of that content only want access to some of it. It is not for those submitting to filter, but for those accessing the content. Have you considered this not as a core feature, but as an option?

Thanks,

Robin

On 3 November 2011 14:00, Hylke Bons < reply@reply.github.com>wrote:

You can have different folders for different things? We can't do filtering on the file level because of how git works. Also not getting some things to some people defeats the purpose of the project a bit. :)

Reply to this email directly or view it on GitHub: https://github.com/hbons/SparkleShare/issues/401#issuecomment-2617256

Dr. Robin Boast Curator for World Archaeology Affiliated Research Scholar, History and Philosophy of Science +44 (0)1223 333515 robin.boast@maa.cam.ac.uk blog: http://rescite.blogspot.com/ Google+: Robin Boast Twitter: robinboast

MAA Museum of Archaeology & Anthropology University of Cambridge Downing Street, Cambridge, UK CB2 3DZ http://maa.cam.ac.uk/

hbons commented 12 years ago

I have thought about this a bit, but concluded this is not the use case I want to cover. Besides the backend not supporting it it adds many layers of complexity. Although I am curious why having a couple of folders for different users isn't sufficient for you.

robinboast commented 12 years ago

That is fair enough, Hylke. It is your system. The point is that the networks we work with are thousands of users, and hundreds of thousands of resources. We cannot determine, in every instance -- even in a relatively small number of cases, what subset of records each user will want. What we are looking for, and what our users are looking for, is a large repository of files that automatically upload and notify users, but each user "subscribes" to a subset through a filter. Up to the point of the filter, your system is perfect, exactly what we are looking for. However, it does us no good without client end filter of some sort.

However, thanks for considering it and I may try to create a module on the front of SparkleShare.

Best,

Robin

On 3 November 2011 15:27, Hylke Bons < reply@reply.github.com>wrote:

I have thought about this a bit, but concluded this is not the use case I want to cover. Besides the backend not supporting it it adds many layers of complexity. Although I am curious why having a couple of folders for different users isn't sufficient for you.

Reply to this email directly or view it on GitHub: https://github.com/hbons/SparkleShare/issues/401#issuecomment-2618410

Dr. Robin Boast Curator for World Archaeology Affiliated Research Scholar, History and Philosophy of Science +44 (0)1223 333515 robin.boast@maa.cam.ac.uk blog: http://rescite.blogspot.com/ Google+: Robin Boast Twitter: robinboast

MAA Museum of Archaeology & Anthropology University of Cambridge Downing Street, Cambridge, UK CB2 3DZ http://maa.cam.ac.uk/

hbons commented 12 years ago

Hopefully you can make it work in some way or another. Anyway, the code's there! :)

fire commented 12 years ago

I believe a SparkleShare that uses git annex (#285) can solve parts of this problem. All annex clones will have a complete list of every file available, but it will not download the entire file. Having a list of all files can be a problem, but you can alleviate this if there was some way to encrypt the specific subdirectory in the repository. However, the good news is it's possible to only get one subdirectory.

I'm available if you wish to contact me.