Add 2024-08-06 notes.

docs/more-information/db-2.0.html

@@ -643,7 +643,15 @@ <h3 class="anchored" data-anchor-id="volume-interface">Volume interface</h3>
 </ul>
 <p><img src="img/manage-volume-enter-data.png" class="img-fluid"></p>
 <ul>
-<li>(<span class="discuss-feature">discuss</span>): How to simplify</li>
+<li>(<span class="discuss-feature">discuss</span>): How to simplify
+<ul>
+<li>2024-08-06: <em>Required</em> variables:
+<ul>
+<li>File name</li>
+<li>Sharing release level</li>
+<li>File type (from extension)</li>
+</ul></li>
+</ul></li>
 </ul>
 <p><img src="img/manage-volume-add-links.png" class="img-fluid"></p>
 <ul>
@@ -682,24 +690,26 @@ <h3 class="anchored" data-anchor-id="sessions-interface">Sessions interface</h3>
 <li>(<span class="remove-feature">remove</span>): Keywords and Tags.</li>
 <li>(<span class="remove-feature">remove</span>): Bars that summarize spreadsheet metadata values.</li>
 <li>(<span class="remove-feature">remove</span>): File names sort by timestamp uploaded.</li>
-<li>(<span class="add-feature">new</span>): Better interface layout for previewing videos.</li>
 <li>(<span class="remove-feature">remove</span>): Video editing within viewer to create highlights.</li>
-<li>(<span class="add-feature">new</span>): Better interface layout for previewing videos.</li>
-<li>(<span class="change-feature">change</span>): Make “set as highlight” feature more visible</li>
-<li>(<span class="discuss-feature">discuss</span>): Simpler tablular interface viewing files, release level, highlight status, etc.</li>
+<li>(<span class="discuss-feature">discuss</span>): Better interface layout for previewing videos.
+<ul>
+<li>2024-08-06
+<ul>
+<li>(<span class="change-feature">change</span>): Create pop-up window for previewing video/audio</li>
+<li>(<span class="discuss-feature">discuss</span>): Could pop-up viewer allow other file-type “previews”, e.g.&nbsp;PDF, docx, txt? Or push to later timepoint.</li>
+</ul></li>
+</ul></li>
+<li>(<span class="change-feature">change</span>): Make “set as highlight” feature more visible. This applies to a file.</li>
+<li>(<span class="change-feature">change</span>): Simpler tablular interface viewing files, release level, highlight status, etc.
+<ul>
+<li>Columns include: File name, sharing release level, file type, size, last modified (optional)</li>
+<li>(<span class="discuss-feature">discuss</span>): Move button to downloading single file to table</li>
+</ul></li>
 </ul>
-<div id="fig-vol-339-slot-1681" class="quarto-figure quarto-figure-center quarto-float anchored">
-<figure class="quarto-float quarto-float-fig figure">
-<div aria-describedby="fig-vol-339-slot-1681-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
-<img src="img/volume-339-slot-16961.png" class="img-fluid figure-img">
-</div>
-<figcaption class="quarto-float-caption-bottom quarto-float-caption quarto-float-fig" id="fig-vol-339-slot-1681-caption-0ceaefa1-69ba-4598-a22c-09a6ac19f8ca">
-Figure&nbsp;1: Timeline from <a href="https://nyu.databrary.org/volume/339/slot/16961/-" class="uri">https://nyu.databrary.org/volume/339/slot/16961/-</a>
-</figcaption>
-</figure>
-</div>
+<p><img src="img/volume-339-slot-16961.png" id="fig-vol-339-slot-1681" class="img-fluid" alt="Timeline from https://nyu.databrary.org/volume/339/slot/16961/-"> - (<span class="remove-feature">remove</span>): Timeline.</p>
+<p><img src="img/session-download-all-files-as-zip.png" class="img-fluid"></p>
 <ul>
-<li>(<span class="remove-feature">remove</span>): Timeline.</li>
+<li>(<span class="discuss-feature">discuss</span>): “Download all files as zip”. With large sessions and/or large files, the zip files are also large and require application resources to create. Are there any third party libraries we could use that would off-load this process? <em>Note:</em> This problem is larger with the “Download all folders as zip” function on the volumes page.</li>
 </ul>
 </section>
 </section>

docs/search.json

@@ -1405,7 +1405,7 @@
     "href": "more-information/db-2.0.html#requirements",
     "title": "Databrary 2.0",
     "section": "Requirements",
-    "text": "Requirements\nThis section provides additional information about the requirements for specific aspects of the Databrary 2.0 application.\n\nSchema\nThe Databrary 1.0 schema can be found here.\nMontrose 1 recommends that we implement separate tables for individuals and institutions. These entities are combined into a single party table in the current schema.\n\n\nUser Access Privileges\n\nAffiliate access to an Authorized Investigator*’s data\nA user may be given privileges to a Volume by an Authorized Investigator.\n\n(remove) No access (default)\n\nThis is redundant for the UI. Remove it there. Retain for backend.\n\n(remove) View and access only public data (Level visible only to Super User; eliminate.)\n(remove) View and access only shared data (Level visible only to Super User; eliminate.)\nRead-only access\nRead/write access\nManager\n\nRead, write, create Private volumes ((new) with supervising Authorized Investigator as the owner)\n(remove) Manager ability to change volume access (change sharing)\n(remove) Manager ability to extend access to Affiliates\n\n\n\n\n\n\n\n\nNote\n\n\n\nPer 2024-05-08 meeting with Montrose, we are likely to implement separate categories for Affiliate privileges “Read”, “Write”, and “Create” and enable various combinations of these, such as “Create” only or “Create” plus “Read” but not write.\n\n\n\n\n\nRegistration workflow\nRegistration consists of multiple steps. The following shows requested modifications to the Databrary 1.0 workflow.\n\nCreate Account\nThe reference page for the Databrary 1.0 registration process is here:\n\nFields are as follows:\n\nFirst and Middle Name (required)\nLast Name (required)\nEmail (required)\n\nAdd instruction text that specifies an official institutional email must be used for this field (e.g., @psu.edu).\nImplement email validation (against existing database of valid institutional email, flag @gmail.com, etc.)\nPermit free-text email if validation fails\n\nAffiliation (required)\n\nType-ahead search of existing database of authorized Institutions.\nIf no matching institution exists, the user can enter a new institution, but should be notified.\nChange label to Institutional Affiliation.\n\n\n\n\nGet Started\n\n\n\nGet Started panel\n\n\n\nRequire user to confirm that they have read and agree to the Databrary Access Agreement.\nLink to the Terms and Conditions of Use.\n\n\n\nConfirm email\n\n\n\nConfirm Email panel\n\n\n\n\nSet Password\n\n\n\nDatabrary Set Password panel\n\n\n\nRequire strong password (increase number of required characters from 7 to 14 characters. 2\nValidate password to ensure that password is strong\n\n\n\nRequest Authorization\n\n\n\nDatabrary Request Authorization panel\n\n\n\nAdd new drop-down menu for new user_position field that requires users to enter their position at their institution. The acceptable values for this field are as follows:\n\nFaculty/Independent Researcher\nStudent\nStaff\nOther\n\nIf user_position is in {‘Student’, ‘Staff’, ‘Other’}\n\nShow research_sponsor text field\n\nAdd instruction text asking user to type the name of the person who is their research sponsor or supervisor; the entered text should use look-ahead search to match to Authorized Investigators currently active on Databrary at the user’s specified institution.\nIf the search succeeds, the user can select the name of their research sponsor.\n\nGenerate a request for authorization from the current user to the research sponsor; cc the current user.\nProvide the user feedback that this request has been sent.\n\nIf the search fails, the user can enter the name of their research sponsor, but warning text appears: “This research sponsor cannot be found.”\n\nAsk the user to enter their research sponsor’s institutional email address.\n\nValidate that address as above.\n\nConfirm that the user wants Databrary to send a request to register email to the user’s research sponsor.\n\nIf yes, send the email to the research sponsor and cc the current user.\nTO-DO: Draft this email.\n\n\n\n\nIf user_position is “Faculty/Independent Researcher”\n\nShow new text field user_institutional_profile and ask user to enter the URL for their institutional profile page.\n\nAdd explanatory text: “Databrary requires that we confirm a new user is eligible for Authorized Investigator status. Please provide a URL to your personal profile page at your institution to assist us in verifying your status.”\n\nIf user’s institution is not in Databrary’s database of authorizing institutions…\n\nAsk user to enter information into two new (optional) text fields: institution_authorizing_official_full_name for the full name of the institution’s authorizing official and institution_authorizing_official_email for that person’s email.\n\nIf user’s institution is in the Databrary database of authorizing institutions…\n\nShow text saying “institution has active users on Databrary. Here is a link to other users from institution on Databrary: . Our staff will work with you and your institution to expedite your authorization.”\n\n\n\n\n\n\nVolume interface\n\n(new): Create bibliographic contributor field. Allow sorting of authors.\n(new): New volumes have a single owner who must be an Authorized Investigator.\n\n\n\n(remove): “Does this valume correspond to a published paper…” and related look up published paper or resource; complete reference info. Will enter linked resources in Add Links tab below.\n(remove): “Add keywords” interface (push to >2.0)\n(future): Pull keywords from related/linked articles\n\n\n\n(change): Default Volume access to Private\n(change): Separate (single) volume owner from Collaborators. Allow transfer of ownership here.\n(remove): “Extend access to … affiliates” checkbox and related functionality.\n(remove): “Investigator (read/write/share)” option for collaborators.\n(change): Make “Read only” default access level for all added Collaborators.\n(discuss): Add expiration date for access to volume for all collaborators.\n\n\n\n(discuss): How to simplify\n\n\n\n(discuss): How to simplify\n\n\n\n(change): “Enter title or paper/dataset citation”\n(future): Way to search Databrary for related datasets.\n\n\n\n(change): Lookup existing funder, but permit user-entered value(s)\n\n\n\n(change): Merge FILE RELEASE LEVELS data with “added on”, “sessions”, “participants” panel\n(change): “HOW TO CITE” field has user editable authors, Databrary specific info is added by the system\n(new): OWNER sub-panel\n(change): Fix column size so that long names and affiliations aren’t cut-off\n\n\n\n(remove): “Create highlight” button and associated workflow. Re-implement in >2.0\n(remove): “Show saved display mode” dropdown and associated workflow. May re-implement some portion in >2.0.\n(remove): “Show summary” functionality. May re-implement some portion in >2.0.\n(remove): Save current display mode functionality.\n(new): Separate interface for Materials\n(discuss): Simpler tablular interface for spreadsheet display?\n\n\n\n(remove): Comments. Consider re-implementing in >2.0\n\n\n\nSessions interface\n\n\n(remove): Keywords and Tags.\n(remove): Bars that summarize spreadsheet metadata values.\n(remove): File names sort by timestamp uploaded.\n(new): Better interface layout for previewing videos.\n(remove): Video editing within viewer to create highlights.\n(new): Better interface layout for previewing videos.\n(change): Make “set as highlight” feature more visible\n(discuss): Simpler tablular interface viewing files, release level, highlight status, etc.\n\n\n\n\n\n\n\nFigure 1: Timeline from https://nyu.databrary.org/volume/339/slot/16961/-\n\n\n\n\n(remove): Timeline.",
+    "text": "Requirements\nThis section provides additional information about the requirements for specific aspects of the Databrary 2.0 application.\n\nSchema\nThe Databrary 1.0 schema can be found here.\nMontrose 1 recommends that we implement separate tables for individuals and institutions. These entities are combined into a single party table in the current schema.\n\n\nUser Access Privileges\n\nAffiliate access to an Authorized Investigator*’s data\nA user may be given privileges to a Volume by an Authorized Investigator.\n\n(remove) No access (default)\n\nThis is redundant for the UI. Remove it there. Retain for backend.\n\n(remove) View and access only public data (Level visible only to Super User; eliminate.)\n(remove) View and access only shared data (Level visible only to Super User; eliminate.)\nRead-only access\nRead/write access\nManager\n\nRead, write, create Private volumes ((new) with supervising Authorized Investigator as the owner)\n(remove) Manager ability to change volume access (change sharing)\n(remove) Manager ability to extend access to Affiliates\n\n\n\n\n\n\n\n\nNote\n\n\n\nPer 2024-05-08 meeting with Montrose, we are likely to implement separate categories for Affiliate privileges “Read”, “Write”, and “Create” and enable various combinations of these, such as “Create” only or “Create” plus “Read” but not write.\n\n\n\n\n\nRegistration workflow\nRegistration consists of multiple steps. The following shows requested modifications to the Databrary 1.0 workflow.\n\nCreate Account\nThe reference page for the Databrary 1.0 registration process is here:\n\nFields are as follows:\n\nFirst and Middle Name (required)\nLast Name (required)\nEmail (required)\n\nAdd instruction text that specifies an official institutional email must be used for this field (e.g., @psu.edu).\nImplement email validation (against existing database of valid institutional email, flag @gmail.com, etc.)\nPermit free-text email if validation fails\n\nAffiliation (required)\n\nType-ahead search of existing database of authorized Institutions.\nIf no matching institution exists, the user can enter a new institution, but should be notified.\nChange label to Institutional Affiliation.\n\n\n\n\nGet Started\n\n\n\nGet Started panel\n\n\n\nRequire user to confirm that they have read and agree to the Databrary Access Agreement.\nLink to the Terms and Conditions of Use.\n\n\n\nConfirm email\n\n\n\nConfirm Email panel\n\n\n\n\nSet Password\n\n\n\nDatabrary Set Password panel\n\n\n\nRequire strong password (increase number of required characters from 7 to 14 characters. 2\nValidate password to ensure that password is strong\n\n\n\nRequest Authorization\n\n\n\nDatabrary Request Authorization panel\n\n\n\nAdd new drop-down menu for new user_position field that requires users to enter their position at their institution. The acceptable values for this field are as follows:\n\nFaculty/Independent Researcher\nStudent\nStaff\nOther\n\nIf user_position is in {‘Student’, ‘Staff’, ‘Other’}\n\nShow research_sponsor text field\n\nAdd instruction text asking user to type the name of the person who is their research sponsor or supervisor; the entered text should use look-ahead search to match to Authorized Investigators currently active on Databrary at the user’s specified institution.\nIf the search succeeds, the user can select the name of their research sponsor.\n\nGenerate a request for authorization from the current user to the research sponsor; cc the current user.\nProvide the user feedback that this request has been sent.\n\nIf the search fails, the user can enter the name of their research sponsor, but warning text appears: “This research sponsor cannot be found.”\n\nAsk the user to enter their research sponsor’s institutional email address.\n\nValidate that address as above.\n\nConfirm that the user wants Databrary to send a request to register email to the user’s research sponsor.\n\nIf yes, send the email to the research sponsor and cc the current user.\nTO-DO: Draft this email.\n\n\n\n\nIf user_position is “Faculty/Independent Researcher”\n\nShow new text field user_institutional_profile and ask user to enter the URL for their institutional profile page.\n\nAdd explanatory text: “Databrary requires that we confirm a new user is eligible for Authorized Investigator status. Please provide a URL to your personal profile page at your institution to assist us in verifying your status.”\n\nIf user’s institution is not in Databrary’s database of authorizing institutions…\n\nAsk user to enter information into two new (optional) text fields: institution_authorizing_official_full_name for the full name of the institution’s authorizing official and institution_authorizing_official_email for that person’s email.\n\nIf user’s institution is in the Databrary database of authorizing institutions…\n\nShow text saying “institution has active users on Databrary. Here is a link to other users from institution on Databrary: . Our staff will work with you and your institution to expedite your authorization.”\n\n\n\n\n\n\nVolume interface\n\n(new): Create bibliographic contributor field. Allow sorting of authors.\n(new): New volumes have a single owner who must be an Authorized Investigator.\n\n\n\n(remove): “Does this valume correspond to a published paper…” and related look up published paper or resource; complete reference info. Will enter linked resources in Add Links tab below.\n(remove): “Add keywords” interface (push to >2.0)\n(future): Pull keywords from related/linked articles\n\n\n\n(change): Default Volume access to Private\n(change): Separate (single) volume owner from Collaborators. Allow transfer of ownership here.\n(remove): “Extend access to … affiliates” checkbox and related functionality.\n(remove): “Investigator (read/write/share)” option for collaborators.\n(change): Make “Read only” default access level for all added Collaborators.\n(discuss): Add expiration date for access to volume for all collaborators.\n\n\n\n(discuss): How to simplify\n\n\n\n(discuss): How to simplify\n\n2024-08-06: Required variables:\n\nFile name\nSharing release level\nFile type (from extension)\n\n\n\n\n\n(change): “Enter title or paper/dataset citation”\n(future): Way to search Databrary for related datasets.\n\n\n\n(change): Lookup existing funder, but permit user-entered value(s)\n\n\n\n(change): Merge FILE RELEASE LEVELS data with “added on”, “sessions”, “participants” panel\n(change): “HOW TO CITE” field has user editable authors, Databrary specific info is added by the system\n(new): OWNER sub-panel\n(change): Fix column size so that long names and affiliations aren’t cut-off\n\n\n\n(remove): “Create highlight” button and associated workflow. Re-implement in >2.0\n(remove): “Show saved display mode” dropdown and associated workflow. May re-implement some portion in >2.0.\n(remove): “Show summary” functionality. May re-implement some portion in >2.0.\n(remove): Save current display mode functionality.\n(new): Separate interface for Materials\n(discuss): Simpler tablular interface for spreadsheet display?\n\n\n\n(remove): Comments. Consider re-implementing in >2.0\n\n\n\nSessions interface\n\n\n(remove): Keywords and Tags.\n(remove): Bars that summarize spreadsheet metadata values.\n(remove): File names sort by timestamp uploaded.\n(remove): Video editing within viewer to create highlights.\n(discuss): Better interface layout for previewing videos.\n\n2024-08-06\n\n(change): Create pop-up window for previewing video/audio\n(discuss): Could pop-up viewer allow other file-type “previews”, e.g. PDF, docx, txt? Or push to later timepoint.\n\n\n(change): Make “set as highlight” feature more visible. This applies to a file.\n(change): Simpler tablular interface viewing files, release level, highlight status, etc.\n\nColumns include: File name, sharing release level, file type, size, last modified (optional)\n(discuss): Move button to downloading single file to table\n\n\n - (remove): Timeline.\n\n\n(discuss): “Download all files as zip”. With large sessions and/or large files, the zip files are also large and require application resources to create. Are there any third party libraries we could use that would off-load this process? Note: This problem is larger with the “Download all folders as zip” function on the volumes page.",
     "crumbs": [
       "More information",
       "Databrary 2.0"