Various indexing web software suggestions
- I index on a 10" Android 10 tablet (a VastKing KingPad SA10), with a bluetooth keyboard, on the Chrome web browser. So, if the software is different on different devices, then it may be good to keep in mind my situation.
- These are answers. They're not questions. Please treat them as answers.
#1: Allow indexers to specify a reason for returning a batch. This reason will not be visible to other indexers, but will be to help the writers of the indexing instructions know how they can improve, clarify, and disambiguate their instructions.
#2: Allow the sidebar's width to be adjusted. It's too wide in many cases, and covers too much of the image.
#3: Allow the top bar to autohide. It takes up too much space that I need for viewing the image.
#4: Allow indexers to go back to previous batches and make edits, ideally for at least a few days, unless they've already been reviewed or something (sometimes I realize I did something wrong only after I've submitted the batch).
#5: Make a key that says what all the button images mean.
#6: If they don't already exist, make *lots* of keyboard shortcuts (yes, even for Android). But make it so they're not enabled by default, since people who aren't using them could accidentally do problematic stuff. Easy access to the keyboard shortcut documentation would be nice.
#7: Allow us to view the image on one device and index it on another (without the image showing up on the device where it's being indexed).
I would like to comment on #1, #5, and #6 of your “answers” / suggestions. I might make a separate post for comments and/ or questions on the others.
#1) Give Reasons for Reindexing: This exists already. Go to Help>Labs and activate the alternative option to send a batch back for Reindexing with reasons. Then refresh your browser (curly arrow or F5 - not sure if the latter works on Android with keyboard)and now next time you click “Reindex Batch” you will get the form below instead of the usual one. Sometimes selection this “experimental” option doesn’t “stick” and you’ll see the standard form. Just go back to Labs and activate again.
#5) Key to the Horizontal toolbar. Here is one below that I’ve made:
#6) Guide to the existing Keyboard Shortcuts:
Here is a link to one provided by the system:
Here is one I made that is compact and convenient for printing. Two jpg pages.1
Comments on #2 and #3
#2) if you’re referring to adjusting the width of the Form Entry Panel, you can adjust it (to a point - there is a minimum size allowed). See the screenshot below from my iPad. You press and slide it back and forth, adjusting the screen real estate allocated to the form vs the image.
#3) Allow the “top bar” to autohide. If you’re referring to the Horizontal toolbar, you can hide or show it by going to Data Entry, and selecting or de-selecting “Show Toolbar.” On an iPad the “hamburger” icon shows and hides the drop down menu ( Batch, Data Entry, Help) at least in one of the screen orientations). If you’re referring to the address bar, consider switching to a “full screen browser. There are several available for the iPad/ IOS that work pretty well. Maybe there are some for the Android system.
I’ll stop here for now.1
Evidently with some Java hacks you can make/allow Chrome to be full-screen on an Android tablet. I didn’t edit my original comment to include this remark because doing that often messes up images posted in the comment.0
I like suggestion #4 - to pull back an already-submitted batch and revise the Indexing (or perhaps even Review work). I know that the Development Engineers have been deluged with suggestions over the years, so I wouldn't expect any particular suggestion to be implemented anytime soon (including my many suggestions). On second thought, maybe they could implement this suggestion of yours as a form of Shared Batch, where if the Indexer has the Batch Code for a batch, and a Reviewer hasn't claimed the batch, that Indexer could open it for Edit and re-submit after making corrections. This "permission to edit" capability could be timed to expire at the normal expiration date of the batch so as not to get around the expiration date process. So the Submission process isn't final until a Reviewer has claimed the batch. Perhaps this wouldn't be too difficult to implement. I don't know.
I’ve experimented with #7. By judiciously moving the Entry Panel to the left or right on the primary and secondary devices (the three dots options), the presence of the image on the second device might not be a showstopper. Or, you can always use Row Entry mode on one device (say the Secondary device), thus allowing practically the full screen for the image. And then use Form Entry Mode on the second (Primary) device- where the entries are made).
Honestly, I still prefer indexing on my Desktop PC vs. my iPad - even with a keyboard on my iPad.
Thanks for all your insights and things.
Regarding #1, that's cool that they have the feature about reindexing feedback (I didn't know that). However, I was talking about submitting reasons for returning a batch, which is different (for that, I would only want a comment box and a submit button, since the reason is likely to be pretty unique every time, unless it's another batch from the same project, with the same reason--which might be redundant).
So, the reindexing feedback is about feedback on what another indexer did. The returning a batch feedback would be about how the project instructions could be improved such that fewer people will need to return batches in future (due to ambiguity and/or insufficient instructions).0
I found a setting on my tablet that might free up a little real estate on my screen. I haven't tried it yet; the indexing system is partially down for maintenence. Here's how (in Android 10): Go to Settings->Display->Advanced->Display size and then drag the thing to the left so it says small. I figure this will probably shrink everything but the image a little.0
When you find problems with the project instructions, the best place to post those would be on the Q&A page for Indexing. There are moderators there who can get in contact with the project managers or the Indexing Operations folks so they can review your concerns. Always hold on to the batch where you have found the problem and share the batch code and the link when stating your case for insufficient instructions or ambiguity. It is really helpful to them to know when there are problems with the instructions.1