globus/data_facility_enrollment_demo

data_facility_enrollment_demo's Issues

Verify a given guest collection has an ACL set properly

Given a guest collection uuid, check to make sure it has the proper ACL set properly:

https://github.com/globus/data_facility_enrollment_demo/blob/main/data_facility_enrollment_demo/gcs.py#L32

Add view logic for choosing an existing mapped collection or creating a new collection

Upgrade https://github.com/globus/data_facility_enrollment_demo/blob/main/data_facility_enrollment_demo/views.py#L16 for attempting to choose a collection from #2, or alternatively creating a new collection if the user wants to do that instead or no other Guest Collections exist for the user to choose.

Consider adding an "Admin Role" on the newly created Guest Collection

When a new Guest Collection for a user is created, add the Admin Role to the collection in addition to the Globus Group.

UI/UX Overhaul

• Take off Globus Portal Framework
• Remove wording around "Guest Collections"
• Remove extra "Globus" references, and other things that the user doesn't need to know about
• Improve wording around landing page

Add instructions in README for spinning up project and deploying via Docker

Currently there is no README! Add a basic README to provide instructions on spinning up a new project, including creating a new search index and adding any resources needed to get the basic demo working. Currently those include:

• Creating a new Search Index
  • globus search index create using the Globus CLI
• Creating one or more Mapped Collections for demonstrating creating Guest Collections
  • Creating a new GCS Instance: https://docs.globus.org/globus-connect-server/v5.4/quickstart/
• Creating a GUEST_COLLECTION_REQUIRED_GROUP
  • Groups are assigned to the newly created Guest Collection in order for the source collection to write to it
  • Developers can create these groups here: https://app.globus.org/groups
• Creating a Globus Developer App
  • Users can create this at: https://app.globus.org/settings/developers

Populate other fields on collection creation

When the new collections are created, we only set the keywords field for the newly created Guest Collection. Populate the new Guest Collection with more of a description on what it should be used for

Create Guest Collection and browse for existing files to choose "Path"

Currently we don't choose a path for a given collection, which would be needed in order to start transfers to the users chosen or created collection. Ideally, we would use the helper pages for a nice way to allow for users to choose paths to use for their mapped collection.

Get Collection by keyword

For steps 6 or 7 of the demo, a user may already have created a Guest Collection. We can find a user's pre-configured collections by doing a lookup like this:

• https://app.globus.org/file-manager/collections
• Keywords match "arc_collection"

Allow fetching collections which match the following keywords above. Change the following function "lookup_gcs_stuff" to return the list of collections:

https://github.com/globus/data_facility_enrollment_demo/blob/main/data_facility_enrollment_demo/gcs.py#L10

Create Guest Collection with Group ACL

Add a method for creating a new collection, and adding a pre-configured ACL to it. For now we'll assume that a group will need to be added to the Guest Collection here: https://app.globus.org/groups/160aac2d-3c58-11ee-a544-6b4261604b9c/about

• UUID: 160aac2d-3c58-11ee-a544-6b4261604b9c

Create testing collections to serve as the "ARC" mapped collections

We'll need three GCS mapped collections to serve as the fake ARC mapped collections where users can create Guest Collections.

Create tracking system for available mapped collections

Create a tracking system for #4. These can be Django models, where each collection is a saved model or a simple JSON array we load at startup. But it needs to list available mapped collections where we can choose a collection for item #3