Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Management Enhancement for Bulk Upload #45

Open
Drumhavoc opened this issue Jul 1, 2022 · 7 comments
Open

File Management Enhancement for Bulk Upload #45

Drumhavoc opened this issue Jul 1, 2022 · 7 comments
Assignees
Labels
extensive enhancement A more extensive enhancement which has big changes important

Comments

@Drumhavoc
Copy link

Drumhavoc commented Jul 1, 2022

Is your feature request related to a problem? Please describe.
Want more control over the file management. Right now, I upload 1 file at a time, manually enter the file/song name and manually enter the composer. This becomes very tedious very quickly. Also, when I upload it, it saves to the install folder in a folder structure I do not control in a location I do not control.

Describe the solution you'd like
The solution I would like would be something like what Sonarr or Radarr did where I specify which root folder Sheetable will "monitor" and then bulk import all the items that aren't in the program yet. It can do a scan of the root folder and bring up a list of all the found files with prefiled Composer and Name information based on Folder and file names. These can be edited by the user to properly reflect which each file is. After import, if any of the song names do not match the file name, you can do a rename option that will organize the files as they were imported.
Future imports can ignore items that are already in the DB and pull in newly added items. The upload process as it is can remain for simple uploads or normal user uploads and will place the new items in the determined folder.
Meta data does not need to be scraped from anywhere, just parsed from the file/folder naming sequence.

image

As an example, in the screenshot above, the "Movie" column would be the 'File/song Name' and "monitor" would be "composer/folder name" and "Min availability" would be like "Custom tags" and "quality profile" would be instument group" and then you can rename files that have been imported to match the file/folder structure you want, something like Composer/year - songtitle - instrument - solo/ensemble

Additional context
Through testing I have had to delete my DB file multiple times losing all the work I did and needing to reupload each of the files. This would allow me to recreate my DB all at once and almost instantly by just pointing to the root folder that holds all the uploads. Aside from the need to restart the application, the ability to mass import will be critical for people with large libraries that they already have well organized and just want to have remote access to them. I use Unraid and the folder for storing the files is on my cache drive instead of on my parity protected data array. While pdf's are small, I expect a large collection that I don't want hanging out on my cache drive and would like to point the program to a share on the array.

@vallezw
Copy link
Member

vallezw commented Jul 2, 2022

Hey, thanks for the Issue. This is definitely one of the more important ones. I already thought of implementing stuff like this, because it's basically a must-have and way cleaner than. Therefore this will be my next task after finishing the user management stuff. Although this will probably take a few weeks since I'll have to rewrite the whole sheet handling process etc. in the backend.
This is still a very important implementation and I'll start a PR soon.

@vallezw vallezw added the extensive enhancement A more extensive enhancement which has big changes label Jul 2, 2022
@vallezw vallezw self-assigned this Sep 5, 2022
@NwaforAugustine321
Copy link

@Drumhavoc I would like to work on this task with @vallezw if not yet done or assigned.

@vallezw
Copy link
Member

vallezw commented Jan 8, 2023

@Drumhavoc I would like to work on this task with @vallezw if not yet done or assigned.

Hey @NwaforAugustine321,
also over here thanks for the interest. I currently do not have time to develop a lot on SheetAble, but if you still want to code it alone I can help you on explaining how I was planning to implement it. I would be able to commit here and there, but just want to say upfront that I will not have time to develop a lot on here.
This is an exthensive issue, but would be very worth implementing. If you'd still like to try, then I'd be happy to assist whereever I can.

@NwaforAugustine321
Copy link

@Drumhavoc I would like to work on this task with @vallezw if not yet done or assigned.

Hey @NwaforAugustine321, also over here thanks for the interest. I currently do not have time to develop a lot on SheetAble, but if you still want to code it alone I can help you on explaining how I was planning to implement it. I would be able to commit here and there, but just want to say upfront that I will not have time to develop a lot on here. This is an exthensive issue, but would be very worth implementing. If you'd still like to try, then I'd be happy to assist whereever I can.

OK @vallezw you can go ahead with the requirements and details of your plans on what to achieve so that I will start from there.

@vallezw
Copy link
Member

vallezw commented Jan 8, 2023

@NwaforAugustine321 Should I write it here or do you want to dm it on the discord server?

@NwaforAugustine321
Copy link

I prefer discord. @vallezw

@vallezw
Copy link
Member

vallezw commented Jan 8, 2023

I prefer discord. @vallezw

Alright @NwaforAugustine321 join the server then https://discord.com/invite/QnFbxyPbRj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensive enhancement A more extensive enhancement which has big changes important
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants