Uploaded image for project: 'SEAD'
  1. SEAD
  2. SEAD-1004

Implement Verified and Trial Project Space

XMLWordPrintableJSON

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.0
    • None
    • None
    • Beta 2 Sprint 6

      As the SEAD project team, we want to:

      1. know when new groups join SEAD so that we can reach out (to find out how they want to use SEAD, how they heard about it, and to help them out)
      2. prevent and quickly discover SEAD abuse (e.g. people posting pornography or their wedding photos)
      3. do 1 and 2 without creating onerous burden for users (e.g. we know from 1.5 that having to wait to do something was annoying for users) or the SEAD project team.

      Acceptance Criteria:
      1. Anyone can create an account on SEAD, without approval, upload files, and create collections in their personal space.

      2. The only way to share data with others is through a Project Space.

      3. Anyone can create a Project Space, but the initial status of the project space is "Trial" and that is indicated in the interface.

      4. SEAD team is able to tell when new spaces are created (e.g. could be in an email, could be a listing that only SEAD people can see of the trial spaces, etc... the mode must allow SEAD team to know the list of trial project spaces and when they were created).

      5. System informs Project Space creator that in trial status they are not able to publish data or make data public beyond the project space team; and that a SEAD team member will review their project space for verification (review meaning look at the space and the content in it and reach out to the group to learn more about what they are using SEAD to do). After 30 days if the space has not been changed to verified status, the space and data will be removed. (note: this deletion will happen manually by a SEAD team member, it's not something that the system will do so no code is needed).

      6. In a trial status, project spaces are able to create test publications, meaning the test flag is forced on trial spaces (note: need a separate ticket to define what should happen in general for the test publication process).

      7. While in Trial status the project space and any of the its files do not show up in SEAD listing beyond the project space team.

      8. After moving to verified status, all the full functionality of project spaces becomes available (e.g. publishing and making data publicly available) and the "trial" designation is removed from the interface.

      Questions and Answers (pulled from comments below):

      Question: Are all spaces( both existing spaces & new created ones) in Trial."
      Answer: yes

      Question: there is a statement on the space page says it is trial mode. and I think what you mean is a long one like " This space is in trial mode, you can contact SEAD member for verification and make it public.""
      Answer: Have the text inline under the space name. Text should read, "New Project Spaces are in trial mode, allowing you to take advantage of all SEAD functionality except publishing and making your data public. A SEAD team member will verify your Project Space shortly to make these additional capabilities possible."

      Question: "there is a "verification request" button in "Edit space" page(, or on the space page?). By click this, a email will send to SEAD member. The email contains the link to the space."
      Answer: No, there is no button. This doesn't depend on user action at all. I think an auto generated email to SEAD staff when the project space is created is desirable. The email should contain the link to the space.

      Question: "The SEAD member then go to space page and a verification-confirm button is on the space page. ---> if SEAD member go to this page without click the link in the email, can they see this button?"
      Answer: How about the button is something that any superadmin can see? And they can toggle to verified status

      Question: SEAD member click verification-confirm button,(1) do we send a email to the space's members? If so, who should receive the email? the owner? all members? (2), the statement on space page is changed to " the space is verified. you can set it public in Edit Space". (3) when open Edit Space, the admin of space can see public / private selection.
      Answer: Send an email notification to the project space's members (all of them). We do not need a designation that says "verified"... the trial statement is simply removed. However, it would be good for the email to let people know "Congratulations, your SEAD Project Space has been verified! Your team now has access to the full suite of SEAD functionality, including publishing and making your data public. Please <contact SEAD> if you have questions or feedback."
      Yes, once the space is verified, the admin can now see an option on the edit space page to make public/private, with private selected by default.

      Question: then I think a standalone dataset( not in any space) cannot make itself as public, right?
      Answer: Correct. the only way to make a dataset public is by it being part of a project space.

      Question: then can it be private in trial mode =>by doing so, the user can make sure it is private forever without some change it status intentionally.
      Answer: there is no such thing as trial mode outside of a project space. Yes, a person could keep a dataset private forever by never sharing to a project space.

      Question: How to handle capabilities that are not allowed for Trial Spaces?
      Answer: Trial spaces can't publish (except test publish) and they can't make data public. For publishing, this means that the "testing only" flag is selected and users are not able to deselect it. For making datasets or the project space public, I suggest in trial mode that we hide this functionality until the project space moves to a verified status.

              yanzhao3 Yan Zhao (Inactive)
              dharmrae Dharma Akmon
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Time Spent - 2 days, 6 hours Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - 2 days, 6 hours Remaining Estimate - 2 hours
                  2d 6h