Collections

[jon-myers]

A new affordance for the IDTP that encompasses a number of different enhancements to existing stuff, and brand new stuff.

Basically, this should be a way for users to "collect" a number of items in different categories for 1) personal organization, 2) sharing with others, 3) assigning to a class or student, 4) uploading and working on materials in the IDTP that are private to that user. The kinds of things that can be collected:

• recordings
• audio events
• transcriptions
• saved analysis presets / visualization outputs.

Collections would show up as a tab along the top of the screen, next to "files", "editor", "analyzer" etc. The collection (or collections) that a particular item is associated with would also show up as a searchable and filterable column in the file manager and audio events tab (and also the soon-to-be-implemented "audio recordings" tab, an improvement over the current audioEvents.) Collections should have a permission structure like the proposed one for users, where they can either be public and editable, public and not editable, or private. If pubic + not editable, or private, user should also have the option of assigning whatever permissions they see fit to whichever users they like.

Implementation:

• Make the actual collections tab. This is the place where users can create a new collection. It is also a place where all these things wiil show up. So, basically, will need some sort of mini- file manager component, as well as a mini audio recordings component that will sit inside of this tab, once a collection has been selected.
• Make the audio recordings tab. In addition to being useful on its own, users will also be able to, with the dropdown menu, assign a recording to a particular collection, or remove it from a particular collection. (Can also be removed from the collections tab itself; and perhaps added, via some sort of search?)
• revamp the file manager, such that it is searchable and filterable, and allows you to add or remove files from particular collections.
• Perhaps add utility to analysis tab that lets users save 1) analysis settings, so that the same query can be applied to multiple different transcriptions. and/or 2) save the actual visualizations generated via analyer.
• Will need a new "MongoDB collection" (don't be confused, MongoDB uses the same "collection" nomenclature to describe a group of documents) to store all these things. Also, in each of the other collections (transcriptions, audio events, audio recordings), will need a new attribute, collections, consisting of an array filled with the ObjectIDs of the associated collections, and perhaps also the names. If including the names, shoudl have a way of linking this information in case the user changes the original collection name.

it might also be useful to be able to specify what sort of a collection this is. The categories might be:

• pedagogy
• research
• aesthetic appreciation (personal playlist, basically)
• creative (compositions / personal riyaz etudes)

[jon-myers]

@Dard-Neuman added this plan for implementing collections. If you have any comments / suggestions / other ideas I'm missing here, feel free to add with comments below.

[jon-myers]

First, write some mongodb aggregation scripts to add the collections array to each of the appropriate collections: Audio Events, Recordings, Transcriptions

[jon-myers]

saVerified needs to be migrated from audioEvents to audioRecordings database

[Dard-Neuman]

I'm just ideating, so don't take these as requests. Ashwin is about to send me some lessons. So let's think about this from three audiences: Ashwin, his students (this quarter), ... and the NEH. Pedagogy might have sub-branches (individual lessons, course/class lessons). If a course/class lesson, there should be the institution, course number, and course name, that can be manually entered by the user (Ashwin).

Perhaps then what the students "click" on takes them directly to Ashwin's "collection", where they sign in, and can view course and the lesson. Again, the details are perhaps not right. I can imagine they need to go first towards swara.studio to just sign in. But do think about it from the student's point of view and as something that scales. I'll also continue to think of it.

Of course, we (the royal we, which is to say, you) can do what we can do for now. So whatever you think is the most efficient approach is fine with me. I'm hoping to generate some "official" traffic to the IDTP. Getting students from Ashwin's and Rahul's course (my brother) will help.

pedagogy research aesthetic appreciation (personal playlist, basically) creative (compositions / personal riyaz etudes)

[Dard-Neuman]

Also, there might be a field (column) that separates works in progress from works completed/"published"

[jon-myers]

This has been largely implemented on the branch. What remains:

• Add dbl click for opening transcriptions in editor

• make new modal for making a new transcription from an audio recording, either within an audioEvent or without one. Will include option to add to current collection (if coming from collection modal), or to add to any collection (if coming from transcriptionManager)

• Clone transcription from collectionViewer , via the above modal.

• Finish regular audioRecordings tab by figuring out how to handle upload metadatas in modal.

• explicitPermissions implementation for all recordings, audioEvents, and transcriptions.

• Feeding these explicitPermissions + old school permissions into what gets shown to users in collections.

• searchable / filterable

(would like to get to these things as well ...) -Redoing transcription manager to allow for draggable borders, and different info shown (like mini) -transcription manager serarchable / filterable -AudioEvents redone for draggable borders / different info shown (like mini)

• AudioEvents searchable / filterable
• Different approach to editing AudioEvent (i.e., no more uploading within that modal. Leave that to audio uploads only).

[jon-myers]

Eventually, "publicly editable" will be removed as a category, but not until entire collections branch is pushed to main, so as not to screw up permissions of things currently in progress.