Closed jdeck88 closed 5 years ago
An easier way to implement this...
For project wizard:
ONLY show single sheet and multi-sheet options. We can add a note that if you are contributing to a team you can create a new project under workbench (and add that functionality there).
Then, Remove "keep configuration in sync"? checkbox option. None of these projects will be in sync (only the team projects are). However, add an advanced options heading (or checkbox) that activates the project settings configuration below it.
A couple other things:
okay this is done in 34449b833fae1e6b5df8301eb9d9ed8f23e58a11
I implemented something more similar to the original issue as that was simpler.
You'll need to login as a user other then Biocode to see what a non admin user sees.
When I started configuring my project and chose a configuration, the website hung for times between 5 seconds and 2 minutes.
Maybe change “NexGen Module” to either "MPS Module" or "Massively Parallel Sequencing", or Second and Third Generation Sequencing Module”. “Include fields for associating sequencing data FROM ANY METHOD THAT GENERATES FASTQ FILES with your tissues. Adds the ability to generate NCBI SRA submission packages from uploaded metadata"
Change “Barcoding Module” to “Sanger Sequencing Module”
“Adds the ability to upload FASTA sequences that will be stored in GEOME”
Are you sure allowing the definition to be edited is a good idea?
"By default, the eventID is only unique within an expedition. When selected, the eventID will be unique across all expeditions within the project. MOST PROJECTS WILL WANT TO USE THE DEFAULT SETTING.
5. For all of the Entity Tables: "The available attributes for Event are listed below. You can choose which attributes you would like to appear on your spreadsheet templates. DE-SELECT ALL ATTRIBUTES FOR WHICH YOU ARE SURE YOUR PROJECT WILL NOT BE COLLECTING METADATA. ATTRIBUTES CAN BE DESELECTED MORE TEMPORARILY WHEN GENERATING TEMPLATES” You can also edit the definition and attribute group along with changing the default column order. ATTRIBUTE GROUPS SIMPLY ORGANIZE YOUR ATTRIBUTES WHEN GENERATING METADATA TEMPLATES AND HAVE NO IMPACT ON THE DATA THEMSELVES. Attributes that are required by GEOME can not be disabled.”
For Tissue, under Auto-Generate ID? “Check this box if you would like GEOME to auto-generate tissueIDs from your materialSampleIDs”
There needs to be some text on the “about" page about what expeditions and projects are. Even better if there can also be a shortened version on the project wizard page. I can write this if you want.
All of the customization options are great but really make having more documentation essential. I can help write this. Its pretty obvious to me how everything works, but undergrads for example will have no clue.
This has been implemented in develop. Mostly done. Remaining issues are covered elsewhere.
After spending a week at the GSC meetings and talking to lots of folks, there is still much confusion about Geome’s current configuration options, even among folks who are familiar with the software. After thinking about this a lot, I’ve come up with the following proposal aimed to 1) simplify things so user’s can immediately understand what is happening, 2) enable limited customizations for any user, 3) create perhaps a better model for offering subscription features.
Synchronized Configurations become “teams”. A team is a group of people that work together. Users are invited to join a team with organizations paying a subscription cost to manage multiple users on a team (and perhaps also have the option to upload photos). In the new model, a user would need to be invited to join a team (synchronized configuration) and then we have the obvious path of offering enhanced features to the team configurations. Would need another db table to track members of configurations.
The “New Project” Creation page then becomes
Most of these changes I think are just UI changes but we lets talk.