| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use the error-display utility to get rid of an unnecessary
error-handling function.
|
|
Check whether a token has expired before attempting to use it. Clear
the session if the token has expired.
|
|
|
|
|
|
for table when fewer than 2000 samples
|
|
2000 samples
|
|
fetching group name
|
|
|
|
fit up to 6 digits)
|
|
fit up to 6 digits)
|
|
|
|
|
|
|
|
|
|
This reverts commit ce3568ce8e33a7ad1e722d42261913b5649df27f.
It turns out we only ever save the approved commits in the database,
so there is no point in adding the extra data to indicate that.
This has been documented[^1] for the future.
1:
https://github.com/genenetwork/gn-gemtext-threads/commit/4e016e43fd05202287730915d129daaed1a02efc
|
|
Mark all Publication metadata edits as automatically approved.
|
|
Use etc/default_settings.py to setup defaults for the application.
Check for mandatory settings and notify users if any of the mandatory
settings are not defined.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The original code (using the homebrew ORM system) would simply ignore
values that were `None` when doing updates - the new code using direct
queries was not.
My (fredmanglis) initial fix to provide a default for values in DB
that did not accept NULL was incorrect; instead, I needed to remove
any key-value pairs from the incoming data that were set to `None` to
fix the bug.
The fix still feels incorrect: maybe we should do direct comparisons
for all old-new value pairs, and set the data to be updated based on
the differences, rather than relying on `None`s.
|
|
including 'chr'
As far as I can tell, the regex from before wasn't necessary; it seems like a simple matter of extracting the 'chr' substring from the chromosome search term
|
|
Provide a means to paginate the data items in the resources page.
|
|
|
|
Fetch the `metadata_audit` trails for phenotypes and probesets using
direct queries rather than the ORM-dependent functions.
|
|
Create a 'metadata_audit' record with a direct query rather than using
the ORM-dependent function to create it.
|
|
|
|
Ensure that changes the database are committed if the query is
successful, or rolled back if not.
|
|
For editing, ensure the user is logged in before even attempting to
check the authorisation privileges.
|
|
Display the "Edit" button for all the users to ensure that they are
aware of the feature.
|
|
Protect the actual "approve" or "reject" steps, rather than just the
UI elements.
|
|
* Add missing `.now()`
* Provide defaults (not `None`) for required fields
|
|
Replace the ORM functions for fetching and updating the publication
with non-ORM equivalents.
|
|
|
|
|
|
traits export
|
|
Avoid the use of the ORM code for fetching data from the database, and
instead use direct queries that indicate easily what is being fetched
from the database.
|
|
Use the reworked `retrieve_phenotype_group_name` to fetch the group
name for phenotype datasets.
== Bug Description ==
There was a subtle bug in the original calls to `retrieve_group_name`
function where the `dataset_id` was passed in as an argument, rather
than the group id.
For some Datasets, the `group_id` and `dataset_id` share the same
value, and would end up querying the correct values, but that was a
fluke where doing the wrong thing ended up with the expected values.
This commit fixes that by using the reworked function, which does the
correct indirection from `dataset_id` to the appropriate `group_id`.
See
https://github.com/genenetwork/genenetwork3/commit/088b6181457ef4e528b7dcbf04b7aca29b274d1f
for the reworked function.
|
|
|
|
Serialize values to JSON using the custom encoder that is aware of
data types the default encoder might not be aware of.
|
|
Change the input elements from all "<textarea ...>" to more closely
adhere to the data that each element is concerned with.
|
|
Assign the value to group within the db connection's context
manager. Initialise the group to an empty tuple at the very begining.
Fixes the error noted in
https://github.com/genenetwork/gn-docs/blob/master/api/questions-to-ask-GN.md
and should now allow the curl invocation:
curl -s https://genenetwork.org/api/v_pre1/group/BXD
to work as expected.
|
|
|
|
The `str.isnumeric()` function returns false for numbers such as
'9.99', '88.8' etc. This commit provides a slightly more robust check
for strings that are numbers. It will fail for numbers with exponents
though.
|
