diff options
| -rw-r--r-- | TODO (renamed from next_thoughts.txt) | 0 | ||||
| -rw-r--r-- | notes/plan.txt | 47 | ||||
| -rw-r--r-- | plan.txt | 41 | ||||
| -rw-r--r-- | tests/test_backend.py | 2 |
4 files changed, 41 insertions, 49 deletions
diff --git a/next_thoughts.txt b/TODO index 8c7d12fc..8c7d12fc 100644 --- a/next_thoughts.txt +++ b/TODO diff --git a/notes/plan.txt b/notes/plan.txt index 005cc84a..33b40663 100644 --- a/notes/plan.txt +++ b/notes/plan.txt @@ -1,10 +1,41 @@ -sqlalchemy schema -records (python library) -python classes -basic tests -flask http api -more tests -flask webface -dump tool +Avoiding ORM and splitting into two apps seems to be like making water flow up +hill. Going to just make this a generic flask-sqlalchemy thing for now. +- backend test setup: generate temporary database, insert rows (?) + +backend/api: +- first-rev schema +- json_blob table (by sha1) +- create work, release, etc +- get by ID + +tooling: +- query tool: by fc id, doi/issn/etc + +importers: +- crossref +- pubmed +- dblp +- "norwegian" journal list +- scihub hash list +- author list? + +webface: +- creators and editors for: + works + releases + files + people + containers + +#### Open Questions + +How to create multiple cross-referenced entities at the same time? Eg, work and +release, with release referencing work. work_id isn't allocated/indicated until +merge-time. As a work-around, could have a temporary work_rev_id column which +gets overridden during merge. + +Mechanism for skipping edit group stage. Propose always having edit rows +generated, containing appropriate metadata, but certain bots can skip creation +of edit group. diff --git a/plan.txt b/plan.txt deleted file mode 100644 index 33b40663..00000000 --- a/plan.txt +++ /dev/null @@ -1,41 +0,0 @@ - -Avoiding ORM and splitting into two apps seems to be like making water flow up -hill. Going to just make this a generic flask-sqlalchemy thing for now. - -- backend test setup: generate temporary database, insert rows (?) - -backend/api: -- first-rev schema -- json_blob table (by sha1) -- create work, release, etc -- get by ID - -tooling: -- query tool: by fc id, doi/issn/etc - -importers: -- crossref -- pubmed -- dblp -- "norwegian" journal list -- scihub hash list -- author list? - -webface: -- creators and editors for: - works - releases - files - people - containers - -#### Open Questions - -How to create multiple cross-referenced entities at the same time? Eg, work and -release, with release referencing work. work_id isn't allocated/indicated until -merge-time. As a work-around, could have a temporary work_rev_id column which -gets overridden during merge. - -Mechanism for skipping edit group stage. Propose always having edit rows -generated, containing appropriate metadata, but certain bots can skip creation -of edit group. diff --git a/tests/test_backend.py b/tests/test_backend.py index c4e67a93..23016e09 100644 --- a/tests/test_backend.py +++ b/tests/test_backend.py @@ -43,6 +43,8 @@ class FatcatTestCase(unittest.TestCase): #rv = self.app.get('/v0/work/rzga5b9cd7efgh04iljk') #assert rv.status is 404 + return pytest.skip("need to put first") + # Valid Id rv = self.app.get('/v0/work/r3zga5b9cd7ef8gh084714iljk') assert rv.status_code == 200 |