For public downloads make sure there's messaging that you don't need to enter user/pw. Also make script work w/o user/pw for public data. Capture who is trying to get the data using a prompt.

EDRN / labcas-ui

User Interface for the Laboratory Catalog and Archive Service (LabCAS)

Apache License 2.0

0 stars 0 forks source link

For public downloads make sure there's messaging that you don't need to enter user/pw. Also make script work w/o user/pw for public data. Capture who is trying to get the data using a prompt. #174

Open yuliujpl opened 1 year ago

yuliujpl commented 1 year ago

🤔 Tell Us About the Feature

Replace this with a clear and concise description of the problem you're tying to solve; for example: I'm frustrated when … or I wish it were easier to …

🎇 What Solution You'd Like

Here, put a clear and concise description of what you want to happen.

〽️ Alternative Ideas

If you'd like, put in a description of any alternative solutions or features you've considered.

🗺 Context

Add any other context or screenshots about the feature request here.

hoodriverheather commented 1 year ago

@yuliujpl It's fine to push this to happen after NIST sprint!

One other place we should think about capturing name and email on public download is if the file is smaller and is downloaded via browser.

yuliujpl commented 1 year ago

@hoodriverheather taking a further step back, should we just capture download analytics comprehensively then? Whoever downloads what and stats associated with them? That way the download tracking is centralized but it's just different ways to get user data either via login or via per-download name/email form they have to fill out?