Closed sdash-github closed 4 years ago
I am happy to make a first attempt at customization (for your review).
A few thoughts about this.
-- The PB (PeanutBase) image at the top left is sort of the representative image we have been using in presentations and posters. (https://peanutbase.org/sites/all/themes/peanutbase_theme/images/peanutbase_logo.png) -- Along with this the header color scheme and the PeanutBase text will make it look like part of PeanutBase (guiding theme here is: As much as possible it should not look like foreign to PB).
-- We have successfully used, at PB and LIS, Iframing independent sites into a PB page to give it a very native look while preserving the top level UI-Navigation elements.
-- Examples are:
(https://peanutbase.org/gbrowse_aradu1.0),
(https://peanutbase.org/germplasm/gigwa), etc.
If we decide to use it within an Iframe, probably it should be when the data is public. So the CSS parts for mainly the header part may be kept minimal and flexible for later consideration.
Let me think about a bit more, as it is being developed, initially, with funding from a project and if we need to acknowledge this fact explicitly. But you can go ahead with what seems suitable to you for now and we revisit the issue later.
from Sven:
Customization is partially accomplished. None of it is checked in yet, but it should be visible on the development site. The plan is to do it in three waves: (a) AraPheno -> ArachisPheno and other species changes, (b) institutional changes, (c) spelling and grammar corrections.
regarding the image question from earlier, maybe the current weedy backdrop could simply be replaced with a solid color and the small image Sudhansu suggested from the main site be put somewhere without trying to make it fill space.
We'll need to gut/replace the news/twitter items. my personal preference would be to just go minimalist, by commenting out blocks where we think we might put something someday, and just focus on core functionality as much as possible. I'd suggest we disable the RNA-seq slider as well as whatever the thingy is that wants to use flash.
Do we want to keep any of the links on the Links page? Some are Arabidopsis-centric.
Besides PeanutBase, are there any we should add? (for example, the Community links on PeanutBase)
I do not see an easy way to guarantee that the (small) peanut part of the background image will be visible. See what you think of the one I have up now. Some actual peanuts appear as you scroll down.
very peanut-ty, but a bit hard to read the text. I'll defer to Sudhansu on questions of style, though.
I am working on a quick and simple mockup of the front page for Sven with the idea that it can be iframed in PB when necessary.
I made a simpler version combining your suggestions, see what you think of it.
Here is a GoogleDrive slide that should give you an idea of a simple interface. https://docs.google.com/presentation/d/11KW-OFo0IYQQ2a--P1bH7LXmViNp-tOoWfFGf1HIZC4/edit#slide=id.g828d4cbe32_0_80
I will leave the background like this for now, and move on to replacing the AraPheno institutions and links.
But do you plan to revisit and change the look later?
Yes, we can evolve it as we go.
I started customizing the institutional links, and removed AraPheno news items. Is there a peanut Twitter feed?
Yes, pl see (https://peanutbase.org) footer (https://twitter.com/peanutbaseorg)
I replaced (or commented out) institutional links over the weekend, and corrected the most obvious spelling and grammar mistakes this morning. Still to do:
Do we have a DataCite account (or "prefix")? https://search.datacite.org This is for linking studies to citations.
For now, I replaced all uses (as opposed to mentions) of "arapheno.1001genomes.org" in our HTML files with "
As far as I am aware we haven't used datacite yet for either LIS or PB. We have been using a pubmed id straight.
On 2020/4/1 4:12 PM, svengato wrote:
Do we have a DataCite account (or "prefix")? https://search.datacite.org This is for linking studies to citations.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/legumeinfo/ArachisPheno/issues/3#issuecomment-607492101, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4A465IMXPLGM7WYHEVI6DRKOU3HANCNFSM4LVGVGYA.
Okay, I will look into replacing it with PubMed.
Please let me know if we need more (or less) institutional links before the presentation (see the About and Links pages).
-- My affiliation is NCGR, not ISU. -- "ArachisPheno is a XXcentralXX repository for population scale phenotype data for//Arachis//(peanut) species."
Can you give me admin level access to change some of these type of contents or just lead me to the html/template file that I can edit when I get in the mood. Thanks.
The mail to field should be set to peanutbase-contact@iastate.edu peanutbase-contact@iastate.edu instead of just me or Andrew. These are the sort of things I can change later.
On 2020/4/3 5:08 PM, Sudhansu Dash wrote:
-- My affiliation is NCGR, not ISU. -- "ArachisPheno is a XXcentralXX repository for population scale phenotype data for//Arachis//(peanut) species."
Can you give me admin level access to change some of these type of contents or just lead me to the html/template file that I can edit when I get in the mood. Thanks.
-- "ArachisPheno is a XXcentralXX repository for population scale phenotype data for//Arachis//(peanut) species."
XX = remove?
Can you give me admin level access to change some of these type of contents or just lead me to the html/template file that I can edit when I get in the mood.
html/home/about.html html/home/links.html
Yes, remove. I couldn't immediately find any markup for strikethrough.
Feel free to make those institutional changes (depending on mood).
e-mail is now configured correctly, at least for this development version. For example, ArachisPheno automatically sends the user a status message when they submit a study or it gets curated or published.
The Download Database feature (from the Home page) now works (except for some issues with the PLINK output, which should be fixable). As in the original AraPheno, it only downloads a preexisting database archive, it does not generate one on the fly. To generate such a snapshot, run
python manage.py generate_database_dump
from the command line (from the ArachisPheno/arapheno directory).
However, this earlier issue
Here is a GoogleDrive slide that should give you an idea of a simple interface. https://docs.google.com/presentation/d/11KW-OFo0IYQQ2a--P1bH7LXmViNp-tOoWfFGf1HIZC4/edit#slide=id.g828d4cbe32_0_80
omits the Download Database, Take a Tour, and Feedback & Issues features. Let me know if you really want to remove those.
Tentative changes - let me know if they satisfy the above requests.
Looks like we can get the data via REST API without having to login-- haven't tested thoroughly though? Can something be done about that, at least tentatively?
Looks like we can get the data via REST API without having to login--
Confirmed - I will prioritize fixing that.
The REST API should be secure now - try it while logged out.
The REST API should be secure now - try it while logged out.
Yeah, can't get to it incognito; works.
- The idea is not to remove, but to gradually introduce them as we go and feel the necessity.
- Therefore, hiding those interfaces is the ideal solution for now. And please document how/where you hid them so that I can revisit them later.
To restore the Data Download and Take a Tour features, undo the relevant HTML comment tags from this commit (lines 69 & 74, 87 & 95, and 106-107): https://github.com/legumeinfo/ArachisPheno/commit/f5503faaf66fa7b5274d5f33617879f63a17b6ef
Shall we close this one and split off individual issues?
Yes, if you want. We can always start a new issue for other customization.
The ArachisPheno doesn't have to be an exact replicate of the Arabidopsis portal. We will need only certain features, at least, in the beginning. This issue is to help us gradually settle on which features, UI included, we need. The features list should evolve as we work through the site and the data we have keeping in mind the flexibility factor for future needs.