[x] Refactor the WebScience.Studies namespace to the WebScience.Measurements namespace and update README.md. This will close out #40.
[x] Since there are so many study concepts in development (both at Princeton and at the other academic groups participating), each of which will become a separate extension, it seems time to split the library functionality from the study-specific logic. Here's what I'd propose:
We maintain one repository for the WebScience library. Each study can then have its own repository, which will include the library using the ordinary git dependency features (e.g., submodule or subtree).
We create a new repository that's specific to the news/disinformation study. The users and permissions on that repository should be identical to those on the current repository.
As the other study concepts progress, each gets a new repository, again with identical users and permissions (at least for Princeton).
If a study involves functionality that other studies might want, we can upstream that functionality to the WebScience library.
I'm marking this as assigned to @akohlbre, since she's leading the implementation. We should definitely get input from @biancadanforth before making these changes.
[x] Refactor the
WebScience.Studiesnamespace to theWebScience.Measurementsnamespace and updateREADME.md. This will close out #40.[x] Since there are so many study concepts in development (both at Princeton and at the other academic groups participating), each of which will become a separate extension, it seems time to split the library functionality from the study-specific logic. Here's what I'd propose:
WebSciencelibrary. Each study can then have its own repository, which will include the library using the ordinary git dependency features (e.g., submodule or subtree).WebSciencelibrary.I'm marking this as assigned to @akohlbre, since she's leading the implementation. We should definitely get input from @biancadanforth before making these changes.