Answers to Script Questions

From Filtered Push Wiki
Jump to: navigation, search

James

Answers from James.

Morphbank

Questions:

Q1. Is it clear to you on this page that clicking submit will result in notification of users of a FilteredPush network?

  • Could have 2 buttons: Morphbank Annotation; Morphbank and FP Annotation
  • In future, may be more than one FP network to submit to.

Q2. Is the text "Submit annotation to Filtered Push." sufficiently clear for domain experts?

  • Could use “Submit annotation to Filtered Push Network” to be more clear...

Q3. On pressing the submit button, do you see the feedback you'd expect about the submission of the annotation to the network?

  • Got no feedback? I do see that the annotation exists on the list but

no way to know that they were sent to FP.

Symbiota

Q1. What would your expectations be about how this page should notify you that the annotation will be sent to users of a Filtered Push network?

  • Again, I hope that submitting to FP becomes ubiquitous so the box

should always be checked. It could also have a button instead. Should have a notification on the determination slip below that says it was submitted.

Q2. In what ways would you expect to be able to control or limit the submission of this annotation to the network?

  • What are the reasons you would NOT want the annotation submitted to

FP? I am not opposed to their being a choice, I just think it should be a very small set of cases. Is there a mechanism to submit later if you do not do it here?

Annotation Processor

Q1: Would you rather have a "landing" page like this one, or skip this page and just have a login page as the Annotation Processor "home" page?

  • I think it depends what reason you are entering the web client. If

you are accessing as a non-node member or remotely accessing without a client then you should get this page. If you are accessing this through one of our clients or are a node member then you can skip it.

Q2: If you do not have an account, would you rather create your own with a form on this site, or have contact details available so that an administrator creates the account for you, or have an administrator create an account for you?

  • You should be able to create your own account which is then

“approved” by an admin.

Q3: Is the answer to Q2 different if you are the sole user of an annotation processor installed with your Specify database, one of several users of an annotation processor installed with a Specify database, or a user of a FilteredPush network instance web client?

  • I assume that if you come here from one of our clients (assuming we

have this direct access) your credentials would allow you to skip the login...

Q4: Is this where you would expect to be after logging in, or would you rather be given a set of options for what to do next?

  • I think a menu might be required as there are several things you

might want to do. Obviously, we need to have some instructions built in to navigate people who are new. If you come from a client expecting to see your annotations then you should land here.

Q5: In what ways would you like to be able to sort/filter/find notifications about annotations you are interested in?

  • Would definitely like to sort on date and from. Summary could be

searchable by category perhaps. These lists could be very long so filtering will be essential. Probably need a few predefined filters for date since last login and/or a specific date, etc.

Q6: Other than reviewing and accepting/rejecting annotations, what functionality would you expect to have present in the annotation processor? Would this be different in an annotation processor installed with a Specify database than in a web client to a FilteredPush network?

  • Is the only way to accept an annotation to map it to local? This will

not be sufficient as there will be cases where the information is accepted by a user but cannot be mapped to local. We will definitely need to be able to do bulk mapping as I believe we had before. There should be an “accept all” and an “accept list,” which could be generated by putting check marks beside all those that will eventually be loaded. These may all have the same “response” which would save curators a lot of time.

Q7: Would you expect to be able to remain logged in indefinitely, or would you expect the annotation processor to log you out after some period of inactivity?

  • I think there should be a set amount of time as people may be doing

this work on open terminals and not private workstations.


Heather

Answers from Heather.

Morphbank

Q1. Is it clear to you on this page that clicking submit will result in notification of users of a FilteredPush network?

  • I think it is clear that it will be submitted to FP, but not that it may also then result in subsequent notifications.

Q2. Is the text "Submit annotation to Filtered Push." sufficiently clear for domain experts?

  • Yes, I think it is appropriate, but could maybe clarify it a bit with a brief description that appears as you scroll over it (as with other fields on that submission page)

Q3. On pressing the submit button, do you see the feedback you'd expect about the submission of the annotation to the network?

  • No, I don’t think it is clear that the submission is ‘submitted’ at all, to either Morphbank or FP.

Symbiota

Q1. What would your expectations be about how this page should notify you that the annotation will be sent to users of a Filtered Push network?

  • I think between the checkbox and the submission confirmation, it should be clear that the change has been submitted to FP. What is perhaps less clear, is what exactly FP is, and how it uses the information (eg. Notify users). If this is an issue, perhaps after submission, there is an extra permission pop-up “this info will be used to notify interested users etc” that the submitter agrees to, or then goes back and un-checks the FP box…..though maybe that type of notification would be a deterrent to some users…..

Q2. In what ways would you expect to be able to control or limit the submission of this annotation to the network?

  • Hmmm, not sure, my first thought is that if someone wants to submit an annotation, they should not be allowed to control or limit where the additional information is pushed, unless it is sensitive/classified information (eg. Locations of rare species).

Annotation Processor

Q1: Would you rather have a "landing" page like this one, or skip this page and just have a login page as the Annotation Processor "home" page?

  • I liked this page, but thought the login fields could be available somewhere on the margins of that first page.

Q2: If you do not have an account, would you rather create your own with a form on this site, or have contact details available so that an administrator creates the account for you, or have an administrator create an account for you?

  • I would rather fill in a form and submit it.

Q3: Is the answer to Q2 different if you are the sole user of an annotation processor installed with your Specify database, one of several users of an annotation processor installed with a Specify database, or a user of a FilteredPush network instance web client?

  • I think if individual users all have unique logins, then the form is appropriate. If multiple users are using one logon, then perhaps there is a field on the form that could indicate this.

Q4: Is this where you would expect to be after logging in, or would you rather be given a set of options for what to do next?

  • I think going right to the notifications is appropriate, as this is the most likely reason people are logging in.


Q5: In what ways would you like to be able to sort/filter/find notifications about annotations you are interested in?

  • I think you would want to be able to search by most of the major fields; genus, species, location (of collection event), annotation author, identified by, institution where specimen is held,

Q6: Other than reviewing and accepting/rejecting annotations, what functionality would you expect to have present in the annotation processor? Would this be different in an annotation processor installed with a Specify database than in a web client to a FilteredPush network?

  • I think you would want to have a feature available to export relevant information for new specimen labels and internal databases

Q7: Would you expect to be able to remain logged in indefinitely, or would you expect the annotation processor to log you out after some period of inactivity?

  • If different users have different permissions, I think it makes sense to be logged out after a period of inactivity.

Jim

Answers from Jim.

Morphbank

  • I chose to annotate the record for Eleutherodactylus diastema. This species has recently been assigned to a new genus, Diasporus, but I was unable to suggest that change because the New Taxon box went to the taxonomy authority file, which is out of date and doesn't offer "Diasporus" as an option. Moreover, the New Taxon box doesn't offer an option of simply typing in the new name, regardless of whether that name appears in the authority file. Even if the authority file contained Diasporus, it would have been a very cumbersome process to find it. Couldn't we instead simply type in the new name? Then, if that name isn't in the authority file, the system can query the user and ask if s/he still wants to go with that name.
  • The system froze when I tried to submit my annotation (I chose the same name from the taxonomy authority file), so I never received any response.

Symbiota

Q1. What would your expectations be about how this page should notify you that the annotation will be sent to users of a Filtered Push network?

  • How about configuring it to automatically send the user an email that contains the annotation? That way, the user has confirmation that his or her annotation was submitted, plus a written record of the content of the new annotation. Also, a box should appear that says something like, "Thank you for submitting an annotation to the Filtered Push network."

Q2. In what ways would you expect to be able to control or limit the submission of this annotation to the network?

  • Why would I want to control or limit the submission of this annotation to the network? What other option is there?

Annotation Processor

Q1: Would you rather have a "landing" page like this one, or skip this page and just have a login page as the Annotation Processor "home" page?

  • I suggest combining these first two pages into one. There's not too much content; a combined page won't look too crowded.

Q2: If you do not have an account, would you rather create your own with a form on this site, or have contact details available so that an administrator creates the account for you, or have an administrator create an account for you?

  • Would it be possible to provide all three options, at least eventually?

Q3: Is the answer to Q2 different if you are the sole user of an annotation processor installed with your Specify database, one of several users of an annotation processor installed with a Specify database, or a user of a FilteredPush network instance web client?

  • I don't know enough to answer this question.

Q4: Is this where you would expect to be after logging in, or would you rather be given a set of options for what to do next?

  • If you're an experienced user, then going here straight away would be appropriate. A novice user, however, likely would have a lot of trouble understanding what everything means and what to do next.

Q5: In what ways would you like to be able to sort/filter/find notifications about annotations you are interested in?

  • By date (of the annotation), by specimen record (i.e., aggregate together all annotations that correspond to a given specimens), by species, and by annotator (person's name).

Q6: Other than reviewing and accepting/rejecting annotations, what functionality would you expect to have present in the annotation processor? Would this be different in an annotation processor installed with a Specify database than in a web client to a FilteredPush network?

  • Ability to print individual annotations, including perhaps generating each one as a pdf.

Q7: Would you expect to be able to remain logged in indefinitely, or would you expect the annotation processor to log you out after some period of inactivity?

  • Should be able to logout manually. Also, have auto logout after a period of inactivity.