Page Comparison

...

1. We will have partners who contribute participants to existing studies, that is, users who download and use our app, and thus are contributing data to a larger population of participants (we propose to call these partners "sub-study partners");
2. Sub-study partners may include their participants in (at least) a couple of ways:
   1. They may assign them an external ID, that in essence should identify the participant's sub-study membership as well;
   2. They may ask existing participants to join the study, such that signing a consent in Bridge should enroll that participant in the sub-study;
   3. Sub-study partners will also create user accounts to manage their own users and external identifiers (only)
3. Sub-study participants may receive schedules (and thus, tasks or surveys) that are unique to their sub-study, but we believe in the main, these changes to the main study will be additive. However, Sage Bionetworks will be responsible for incorporating such changes so that they don't break the main study;
4. Sub-study partners may access their list of participants and/or external identifiers, and can probably do anything an existing researcher can do with those entities... but only those that are in the sub-study. They cannot see participants or external IDs in other sub-studies (or no sub-study);
5. The client app should know the sub-study memberships of a participant in case this is important to deliver the correct UI/behavior;
6. Sub-study membership needs to be exported with all data exported to Synapse. The team that processes the data will use this membership information to create specific repositories for those sub-study partners;
7. All users can be in multiple sub-studies (both participants, and administrative users). It's not clear what the requirements are for this (e.g. should a researcher see all participants in all the sub-studies they are a member of at once, or only one at a time with a mechanism to select their current sub-study?), but these requirements don't radically change the implementation design;

...

Tasks

Clean up accounts to remove GenericAccount and HibernateAccount, and the copying between the two classes (subsequent changes heavily involve the AccountsDao, so it would help to simplify first).

...