Uploaded image for project: 'BrownDog'
  1. BrownDog
  2. BD-2360

Set up approval mechanism for submitted transformations

XMLWordPrintableJSON

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Tools Catalog
    • None

      Currently only a select group in NCSA LDAP can log into the transformations catalog and post transformations for publication. We want to find a way to allow a larger number of people to submit transformations, without allowing garbage entries and without taking a lot of our time reviewing submissions.

       

      All of these can be used in concert, but can also be applied independently. There may be others that are not outlined.

       

      Manual review of submissions

      Pros: Allows us to relax who can submit without allowing all submissions to show up

      Cons: We will have to spend time reviewing submissions

       

      Limit the number of transformations each day

      Pros: Limits the amount of reviews we will have to do

      Cons: If a single user has many transformations at once they will have to spread out the registrations

       

      Query the form fields looking for suspicious values

      Pros: Limits the number of requests we will have to review, has the best potential for limiting problem submission

      Cons: Potentially reject valid values, can take significant time to train an algorithm to find suspicious values, will not catch all problem values

              fredrick Mark Fredricksen
              fredrick Mark Fredricksen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: