The FORUM feature will be discontinued due to lack of use.  If you find this useful please let us know

 

Forums / Reporting Questions and Feedback / Code and Definition in Output

Code and Definition in Output

7 posts, 0 answered
  • David Venditti
    dvenditti avatar
    11 posts
    Registered:
    14 Nov 2012
    04 Jan 2013
    Do we really need both the code and definition for things like conditional comment, capture method, etc. in the output?  It seems that the Spec. Document should be sufficient to define these codes for new users and once familiar with query building and reporting, this exra output is just more data the user will filter out of their data files before using them in any sort of analysis. 

    I understand that the Spec. Document would be tough to keep current; espicially with the number of new instream detectors being installed.  Perhaps look-up tables with codes and definitions would be preferable to redundant columns of data in the output files.

    As always, thank you for the opportunity to put in my $0.02.
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    64 posts
    Registered:
    21 Feb 2012
    09 Jan 2013 in reply to dvenditti
    That is a good question and one that we need the PTAGIS user community's help to answer. It is easy to change the default to display only the code. We do have the validation codes available for viewing and downloading in the advanced reporting tool (go to Standard Reports / Validation Codes to see them), and will also be making them available on the main website in the future. 
    Link to this post
  • David Venditti
    dvenditti avatar
    11 posts
    Registered:
    14 Nov 2012
    10 Jan 2013
    Excellent, Democracy in action.

    I'll cast my vote for only the code
    Link to this post
  • Jeremy Bender
    jeremybender avatar
    3 posts
    Registered:
    29 Oct 2012
    01 Mar 2013
    I have a related question.  When using QueryBuilder2 to build a report, many of the attributes I want to select have multiple options for how they are displayed in the report (ID, Code, Name).  It seems by default that both Code and Name are displayed as described in the original question.  I've utilized the option to select which "attribute forms" are displayed so that I only see them in the form I want.  However, whenever I save the report then re-open it later it defaults back to showing both the code and name for all of the attributes with multiple forms.  It is very time consuming to have to modify the report each time I want to run it in order to avoid having both the code and name output for most of the attributes I use. 

    Is there a way to save the attribute forms I define in building the query so that each time I pull up the report I don't have to redo this step?  Alternatively another option would be separating things like "species name" and "species code" as two distinct attributes you can include in the query, in place of having to select "species" and then later defining which form of that attribute you want to include in the report as it is now. 
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    64 posts
    Registered:
    21 Feb 2012
    01 Mar 2013 in reply to jeremybender
    Yes, there is a way to keep the attribute forms you would like to display. When you save your report, select the "Only filter will be prompted" option under "Save report as prompted." See attached screenshot for details. 

    When you run a report that has been saved this way, you will only be prompted to change filter parameters and any changes you have made to the way attributes are displayed will remain.

    Link to this post
  • Jeremy Bender
    jeremybender avatar
    3 posts
    Registered:
    29 Oct 2012
    01 Mar 2013 in reply to NTancreto@psmfc.org
    Thanks, I will give this a try.  However, does selecting this option also mean that I will no longer be able to edit the actual attributes for that specific query, just only the filters from that point forward?
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    64 posts
    Registered:
    21 Feb 2012
    01 Mar 2013 in reply to jeremybender
    Yes, that is correct. 

    We will be working on making Code-only and Value-only attributes available in the future.
    Link to this post