Article Lock for Event Judging | World Anvil

Remove these ads. Join the Worldbuilders Guild

Article Lock for Event Judging

New Feature Addition · Articles & templates · Created by tlcassis
closed
Article_lock SC_Submission
When we do community events such as Summer Camp, we submit articles as part of the event. These articles are reviewed and "competed" or at least looked at and can win prizes. There should be a feature that helps us (obsessive compulsive perfectionists and those of us who never took the observant feat) to keep from messing with submitted work that is in the process of being reviewed or evaluated. This can take one (or two) forms:   1 an author lock feature OR   2 an instance baseline of submitted articles made at the time the event closes   option1 has a lot of flexibility to apply to ANY reason a worldbuilder might not want to just causally change something even when they can, but it puts the responsibility on them to do it which isn't great for newbie worldbuilders (like me).  It also means that we have to WAIT to mess with our articles until you finish judging... (impatient tapping of foot noise).  This is obviously the best solution IF judging is being done by the community not the WA gremlins...   Option 2 is cleaner for the WA gremlins and makes for less hassle with checking for updates and potentially having discussions and making decisions on whether someone fixing a spelling error is a disqualifying event and having bad feelings in the community about it.  It also lets us mess with our articles while our critical eye is hot and we are actively kicking ourselves about the font size, spelling mistakes etc.  If it's automated people don't resent it if it goes against them (go figure...).  On the other hand, being generous about stupid little stuff is part of building community.     MY SUGGESTED FUNCTIONALITY FOR OPTION 1   The author sets the "article lock" feature that would not allow anyone to modify the article without disabling the lock. it should work something like this:   Create a Feature toggle to lock on/off: authorized authors can use this toggle to set article locks   On Lock on, user must provide text reason the article is locked (like "SC2021 submission") - cannot lock without reason, Could be a pull down menu with text other option for user provided reason)   On attempt to EDIT AND SAVE a locked article error message appears   "Article is locked for change because TEXT PROVIDED BY LOCKER APPEARS HERE" To unlock:"   provide resolution which should be:   "contact AUTHOR HERE" (if the modifier is not an author) OR   "unlock article on something tab under whatever feature location"   Feature toggle should provide positive confirmation the article is locked/unlocked when toggled     OPTION 2   The other option is maybe easier (maybe not) and that is to save off an instance of the current article for each entry subitted to the event at the time the event closes. Then it would not matter at all what we did with the articles once the event closed and we could tweak to our little hearts desire without invalidating our entry. I think this is the easiest way for the community and makes competitions a lot cleaner, but it might be harder depending on what your infrastructure is.
Current score

37/300 Votes · +6200 points

Votes Cast

  • +300

    by William Lord
    on 2022-08-20 16:23
  • -100

    by Chairman Goodchild
    on 2022-08-19 15:03
  • +100

    by Endrise
    on 2022-08-18 09:46
  • +300

    by Rahjar
    on 2022-08-17 15:31
    I just think a copy of the articles submitted, in a place where the judges can access it is what's needed, but this isn't too far off that.
  • +300

    by Logan Mountain
    on 2022-08-16 01:50
    I would love both honestly lol ... but the second one more ... I have found so many things I want to update and fix in my Summercamp articles already and I'm so incredibly ADD I would to be able to fix them now while I remember what they are, or just because I want to satisfy my perfectionism ... so ... yes ... yes please!
  • +300

    by ano19920
    on 2022-08-15 21:09
  • +300

    by MrBauta
    on 2022-08-12 20:10
  • +300

    by PrincessESH
    on 2022-08-10 01:38
  • +100

    by Cassie Storyweaver
    on 2022-08-09 18:11
  • +100

    by A Beloved Goblin
    on 2022-08-09 17:22
  • +300

    by A Thundering Skeleton
    on 2022-08-07 23:03
    Honestly even the accidental autosave can cost you the badge, so YES PLEASE to option 2
  • -300

    by SoulLink
    on 2022-08-07 20:05
  • +300

    by Michael Chandra
    on 2022-08-07 17:35
    There are so many people that don't know updating their submissions past the deadline can even cost them their badge, so I definitely would like some warning support that you can overrule if you really want to.
  • +100

    by scholarmage
    on 2022-08-05 03:21
    This sounds unnecessarily complicated, but has a solid idea behind it. Even something like the ability to choose to turn off auto-save on competition entries during the judging period would be helpful, & then having a confirmation prompt upon hitting save, like "This article is currently being judged in a competition. Are you sure you wish to alter it?"
  • -300

    by themrbeasley
    on 2022-08-03 23:47
    I was happy to continue updating my submissions.
  • -300

    by Scalenex
    on 2022-08-03 19:33
    too complicated and it limits the editorial abilities of WA users. I am stuanchly opposed
  • +100

    by Aegnorindas
    on 2022-08-03 15:24
  • +300

    by KajetanWrites
    on 2022-08-03 14:45
  • +300

    by MissIzette
    on 2022-08-03 13:55
  • -1

    by UnknownWriter88
    on 2022-08-02 23:18
  • +300

    by A Lusty Orc
    on 2022-08-02 14:21
  • +300

    by Ononomad
    on 2022-08-02 08:10
  • +100

    by Afranius
    on 2022-08-02 07:33
  • +100

    by Jontaro
    on 2022-08-02 05:46
  • +300

    by CrazyEddie
    on 2022-08-01 22:43
  • +300

    by BCGR_Wurth
    on 2022-08-01 22:31
  • +300

    by TinkerTech
    on 2022-08-01 22:25
  • +1

    by Tijmuhn
    on 2022-08-01 20:15
  • +300

    by DMFW
    on 2022-08-01 19:25
    Makes sense. Option 1 is the more explicit and maybe has uses outside competitions. Option 2 is easiest for authors as there is no danger of them forgetting to lock articles and I can also see the benefit of continuing to tweak articles whilst they are hot in your imagination which is likely to be during the judging period. I slightly favour option 2 if it is something the devs think can be done but option 1 would also be useful. Or both :-)
  • +300

    by illumiinae
    on 2022-08-01 19:05
  • +100

    by Vibeca
    on 2022-08-01 18:06
    That would be helpful for hopelessly messy minds like mine to keep track of what you're currently not supposed to change.
  • +100

    by Adcheryl
    on 2022-08-01 16:28
  • +300

    by malkuthe
    on 2022-08-01 12:12
  • +300

    by ImoenKim
    on 2022-08-01 11:45
  • +300

    by Vertixico
    on 2022-08-01 08:33
    This is a valid request I believe, not only for accidental edits (because you know... auto save), but especially for worlds with Co-Authors.   It could prevent Co Authors from unknowingly edit an important article (or disqualify one from a competition on accident)
  • +300

    by A Beloved Mlem
    on 2022-08-01 05:26
    I'm so paranoid of messing up an article!!! This sounds like a great idea. I've worked so hard this month!
  • -300

    by A Lusty Velociraptor
    on 2022-08-01 04:17
    it feels too complicated really for something that can be solved easily by dumping all of the articles under a category or temporarily changing their title
  • +300

    by tlcassis
    on 2022-08-01 03:36