Is sharing a knowledge base a good idea?

RemNote Learning RemNote
#1

I’m starting a research project, with (a bit too) many collaborators (>10 people :/). I would like us to use RemNote for a common knowledge base (using PDF highlight and all).

Do you see a contraindication to create a (pro) account, and provide everybody with the login and password?

I know it looks very sketchy doing so, … but I don’t see how to do this otherwise. Maybe that’s even against the “fair use” of RemNote. IDK

Also, what would be the implications regarding the RemNote folder with all the PDF etc?

Any idea?

#2

@Karthikk could you tell me if it’s against the fair use of RemNote to do that?
Also, if you have any insight against doing such thing, please let me know.

Thank you for your time! :slight_smile:

#3

Hey @_yb , we haven’t really thought about the fair policy of usage in this sense. Generally, wouldn’t make sense to use a single account as a KB would be personal.

Nevertheless, we are currently in the experimentation phase for collaborative KBs. Maybe we could work with your team closely and allow you guys to have a shared Team KB (still in alpha) and in return we could benefit from the feedback of the team.

If it sounds good, let me know and we can come up with a plan :slight_smile:

#4

hello @Karthikk,
First, I think it’s nice that you are working on a collaborative approach to RemNote :+1:

On the one hand, I would love to work collaboratively with RemNote: it makes so much sense for team of researchers, I think. On the other hand, I’m not confident that I can bring the team to work on important deliverables based on a collaborative KB if the alpha is somewhat unstable. It’s a job at the end of the day, and we need some “guarantee”. It’s an alpha development, so there will always be some surprises, which I think it’s normal, but my concern is about losing data. Do you think that’s a big possibility?
Also, the team I’m working with has a very diverse profile: most of us are somewhat tech-savvy, but not everybody in the team is. Is that OK for the alpha testing you have in mind?
Edit: also, what are the collaborative features? authorship of text? track-changes? comments? versioning?

Many other questions come to mind, but we can have a talk later on, if this lands at some point.
I’ll simply ask the team if they are willing to have some experimentation with our work process, and if everybody agrees, then I’ll notify you, and we could discuss this further (no sooner than mid-July though). Meanwhile, if you have some info on the stability of the alpha, that might change some minds. Personally, thinking of all the possibilities, I’m quite excited to jump in! :slight_smile: