[EP-tech] Antwort: Re: Antwort: Re: Howto hide sub-fields in workflow

Tue Mar 13 13:00:06 GMT 2018

Hi Adam

sorry confusing you: i thought about the table (class="ep_form_input_grid")
inside the submitter workflow.
Anyway! In the end a 6 line jQuery afterburner was much more easier, than
coding hundereds of lines for render functions, plugins etc.

The other solution - clone a subset and add only this to the workflow -
makes me sick, knowing the same data (hopefully) is holded twice.

Thanks for your help ;-)

Jens

--
Jens Vieler
Zentrale Informatik
Universität Zürich
Stampfenbachstrasse 73
CH-8006 Zürich

mail:  jens.vieler at id.uzh.ch
phone: +41 44 63 56777
http://www.id.uzh.ch

Von:	Adam Field <adam at adamfield.net>
An:	<eprints-tech at ecs.soton.ac.uk>
Datum:	13.03.2018 12:04
Betreff:	Re: [EP-tech] Antwort: Re:  Howto hide sub-fields in workflow
Gesendet von:	eprints-tech-bounces at ecs.soton.ac.uk

Hi Jens

                I’m not sure I understand your question.  Which table?  If
you don’t want subfields to show on output, too, you need to write a
render_output function.

                I suppose the other thing you could do is hide the input
fields with javascript…  Just make sure you don’t save the bits you aren’t
interested in, just in case.

--
Adam

      From: <eprints-tech-bounces at ecs.soton.ac.uk> on behalf of
      <jens.vieler at id.uzh.ch>
      Reply-To: <eprints-tech at ecs.soton.ac.uk>
      Date: Tuesday, 13 March 2018 10:43
      To: <eprints-tech at ecs.soton.ac.uk>
      Subject: [EP-tech] Antwort: Re: Howto hide sub-fields in workflow

      Hi Adam

      well, i can hide or do_whatever on the field while using the
      render_input property - but,  the table and it's heading is still
      there :-( Is it CORE? Any ideas?

      best regards
      Jens
      --
      Jens Vieler
      Zentrale Informatik
      Universität Zürich
      Stampfenbachstrasse 73
      CH-8006 Zürich

      mail:  jens.vieler at id.uzh.ch
      phone: +41 44 63 56777
      http://www.id.uzh.ch

      nactive hide details for Adam Field ---12.03.2018 14:24:46---What you
      neeAdam Field ---12.03.2018 14:24:46---What you need is an input
      renderer.  Set the render_input property on the field, and then I’m
      afraid

      Von: Adam Field <adam at adamfield.net>
      An: <eprints-tech at ecs.soton.ac.uk>
      Datum: 12.03.2018 14:24
      Betreff: Re: [EP-tech] Howto hide sub-fields in workflow
      Gesendet von: eprints-tech-bounces at ecs.soton.ac.uk

      What you need is an input renderer.  Set the render_input property on
      the field, and then I’m afraid you’ll need to write some perl.

      Alternatively, make two fields.  Once simple, with only the things
      that need to be inputted, and one complex with all the other fields.
      Put the simple one in the workflow, and then copy the values across
      to the complex one in the automatic fields function of your dataset.
      That’s probably the simpler way.

      --
      Adam

            From: <eprints-tech-bounces at ecs.soton.ac.uk> on behalf of
            <jens.vieler at id.uzh.ch>
            Reply-To: <eprints-tech at ecs.soton.ac.uk>
            Date: Monday, 12 March 2018 13:11
            To: Eprints Tech <eprints-tech at ecs.soton.ac.uk>
            Subject: [EP-tech] Howto hide sub-fields in workflow

            Hello List

            I have created a dataset with fields in which one field
            (type=compound; multiple=1) has subfields, but not all of them
            are intended for input by the submitters in the workflow. How
            can I hide individual sub-fields?

            Merci Jens
            --
            Jens Vieler
            Zentrale Informatik
            Universität Zürich
            Stampfenbachstrasse 73
            CH-8006 Zürich

            mail:  jens.vieler at id.uzh.ch
            phone: +41 44 63 56777
            http://www.id.uzh.ch*** Options:
            http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
            *** Archive: http://www.eprints.org/tech.php/ *** EPrints
            community wiki: http://wiki.eprints.org/ *** EPrints developers
            Forum: http://forum.eprints.org/ *** Options:
            http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
            *** Archive: http://www.eprints.org/tech.php/
            *** EPrints community wiki: http://wiki.eprints.org/
            *** EPrints developers Forum: http://forum.eprints.org/
      *** Options:
      http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech ***
      Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki:
      http://wiki.eprints.org/ *** EPrints developers Forum:
      http://forum.eprints.org/ *** Options:
      http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
      *** Archive: http://www.eprints.org/tech.php/
      *** EPrints community wiki: http://wiki.eprints.org/
      *** EPrints developers Forum: http://forum.eprints.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20180313/a3c806b4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20180313/a3c806b4/attachment-0002.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3C452961.gif
Type: image/gif
Size: 106 bytes
Desc: not available
Url : http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20180313/a3c806b4/attachment-0003.gif 