Feed overlap not working as expected

Hi @ines,

Continuing on this one,
I have this scenario: for example 10 examples for annotation

two routes:

  • 127.0.0.1:8080/?session=user1
  • 127.0.0.1:8081/?session=user2

But, this creates each user their own dataset.
I want user 1 to annotate 5, and user 2 to annotate other 5.

But, this does not work as expected always. If I open both sessions at the same time, I annotate 5 example from user1, save, exit. Now, if I go to user2, it also shows me the examples that I already annotated through user1.

I don’t want this to happen. Any way?

Yes, this is the default behaviour: user feeds overlap so everyone gets to see the same examples. If you set "feed_overlap": false, the annotations will be sent out without an overlap, meaning that every examples will only be annotated once overall instead of once per annotator.

Here’s the relevant section in the PRODIGY_README.html:

The "feed_overlap" setting in your prodigy.json or recipe config lets you configure how examples should be sent out across multiple sessions. By default (true), each example in the dataset will be sent out once for each session, so you’ll end up with overlapping annotations (e.g. one per example per annotator). Setting "feed_overlap" to false will send out each example in the data once to whoever is available. As a result, your data will have each example
labelled only once in total.

Still, it does not work as expected.
Should user1 exit before user2 start working?

(Moved this to a new topic so it’s easier to find and not hidden in the comments of the other thread.)

Where did you set the setting and what are you seeing? If you start two separate sessions, are both sessions still receiving the same questions?

I set "feed_overlap": false in prodigy.json .
Yes, start two separate sessions at the same time, I annotate 4 from one session, save. And I go to other session, refresh, and still get the previous questions.

Hi @ines,

Seems like it works on two prodigy sessions running on same ports. But fails on different ports. Is this the expected behavior?

Ah yes, that makes sense, though, since you’re running separate instances. The named multi user sessions are specifically intended for running one single instance of Prodigy on one port.

Hi @ines,

Doesn't work for me. I run a single prodigy session on a single port, with "feed_overlap": false in prodigy.json. There is still the same feed in each different named session.

Which version of Prodigy are you running? And are you running one single instance and accessing different sessions via the ?session= parameter?

Hello Ines, I'm having the same issue as the others: feed_overlap = false, one single instance of prodigy on one single port and multiple users accessing it through browser via url like example.com/?session=peter and example.com/?session=paul
It shows the current session but it still sends the same entries to both sessions.

Prodigy version is 1.10.7