Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Software descriptions saveframe should not have default value for sf_framecode #46

Open
jonwedell opened this issue Oct 31, 2018 · 5 comments

Comments

@jonwedell
Copy link
Member

Otherwise the enumerations are not suggested.

@jonwedell jonwedell transferred this issue from bmrb-io/BMRBdep Nov 1, 2018
@elulrich
Copy link
Contributor

elulrich commented Nov 1, 2018 via email

@dmaziuk
Copy link
Contributor

dmaziuk commented Nov 1, 2018

Also keep in mind that summary page scripts look for "sample_1", "sample_conditions_1" and who knows what else (those two are the ones I know of, in metabolomics summary pages), so there may be side effects to dropping those defaults.

@jonwedell
Copy link
Member Author

Also keep in mind that summary page scripts look for "sample_1", "sample_conditions_1"

I wouldn't change the default for all saveframe categories, just this specific one (and only in the context of creating a "new template deposition").

@elulrich - The current state of the dictionary is that the tag _Software.Sf_framecode is a mandatory field, with the ADIT description Software name. Furthermore, the tag is enumerated with a list of software package names. (At least one of them have a space in the name, so that enumeration isn't valid.)

I know we discussed before that ADIT was taking the Software.Name tag and converting it into an acceptable value for the "Software.Sf_framecode" tag. But apparently in the dictionary Software.Name is specified as hidden in the deposition interface. I don't believe we had yet decided on how to handle these sorts of auto-generated Sf_framecode tags.

Do we:

  1. Pre-fill all Sf_framecode tags with just category_name_1 and category_name_2 and so on and capture the real information from the user in a different tag (for example, Software.Name)?
  2. Do it as ADIT did. (Requires updating the dictionary and creating a list of which saveframe categories have this "auto sf_framecode generation" code such that it can be implemented on the new server)?
  3. Other ideas?

My preference is option 1.

@jonwedell
Copy link
Member Author

Also this is related to issues 3 and 16 on the InstantDep Github repo.

@dmaziuk
Copy link
Contributor

dmaziuk commented Nov 1, 2018

There must be an override somewhere as Software name comes up in the interface, with enumeration drop-down, and it's one of 3 required fields in the entire software section.

Also note that there are no saveframes in ADIT, there's only various ID tags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants