-
Notifications
You must be signed in to change notification settings - Fork 19
Windows share mounts
As a user I want to select a windows drive as a source in the Parameter space wizard.
As a user I want to be able to browse a windows network drive in the Parameter Space wizard.
As a user I want to be able to interactively access media files in Parameter Space models from a windows network drive
As a developer I want to have a session mechanism for creating and removing network drives
*As a developer I want to be able to use a server api to browse a mounted network drive
*As a developer I want a modular ui component for browsing windows network drives
A typical Slycat user has a scientific background with minimal knowledge of how to use the unix operating system. Slycat users tend to be working within a windows environment and are expect to either be using chrome or Firefox within this windows environment. Due to user's general emersion in the windows environment they are used to using windows shares and network drives to collaborate and store large data sets
The Slycat software environment needs to provide users a way of interacting and retrieving users data from a windows network drives. The intentions of this new functionality is to give users a new means of accessing their data via windows network drives for creating Parameter Space models
Users will interact with this new functionality by 2 main routes. The first route will be when users are in the Parameter space wizard creating a new model where they will be given the option to get their data from a windows network drive. The other route for the user to interact with windows network drives is when hovering over points in the parameter space model allowing the user to pull media data from the windows network shares.
Slycat server must be able to mount a windows network drive onto the server as the "user" for browsing and downloading files. The system must be able to provide the user a way to interact from the ui with their mounted drive.
A connection will be created to the network drive from the slycat server given a username and password. Slycat will keep track of a user session to manage authentication and drive mounting in couchdb. Slycat shall use the connection and the stored session to mount the network drive for browsing and file transfer to the slycat sever. The server will have an API for communicating with couchdb as well as interacting with and browsing the remote drive. The client will have a UI react module for using the backend API for a user to browse files and navigate folders. The client module will be stand alone and will require no dependency injection into the module. The client module will take a function to return a selected file path too.