• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
CSV Merge
#1
I'd love to be able to merge CSV data into MSP. 

My workflow are:

1.
- design charts in iRealPro
- export playlist to a Linux box
- process using irealcvt to images
- process using irealcvt and scripts to extract key, tempo and style
- collect all data in a CSV file


2.
- write scores in MuseScore
- convert to PDF 
- extract key, tempo and style 
- collect all data in a CSV file

From here I transfer the directories, including images, PDFs, associated audio files and the CSV file, to my tablet. I'm then able to import all songs into collections ignoring duplicates but am then faced with the manual tasks of:

- merging in meta data that has changed
- removing songs that are no longer referenced in the CSV file
- manually referencing audio files 

I've tried combining all songs into a single PDF file and importing the metadata from the CSV file. This works but creates duplicates if performed again meaning that the collection needs to be removed first with the resulting loss of historic set lists.

I'm perfectly capable of writing code to modify the database to my requirements but would like to know if CSV merging is on the development time line or whether it's possible to assist the development team in adding this. 

Kind regards, 
Terry.
Reply
#2
Sorry for the long delay in responding Terry. I haven't really given CSV merging too much thought to be honest. I guess in some ways it's similar to the Sync Library features. I can look into this next year after the iOS version is released. If a lot of users will find this functionality useful, I can raise the priority for when it's implemented. As far as offering your assistance, do you mean with establishing the requirements and design, or do you mean with the actual coding?

Thanks,
Mike
Reply
#3
(07-02-2019, 02:31 PM)Zubersoft Wrote: Sorry for the long delay in responding Terry. I haven't really given CSV merging too much thought to be honest. I guess in some ways it's similar to the Sync Library features. I can look into this next year after the iOS version is released. If a lot of users will find this functionality useful, I can raise the priority for when it's implemented. As far as offering your assistance, do you mean with establishing the requirements and design, or do you mean with the actual coding?

Thanks,
Mike

Hi Mike,

Thank you for your response.  I've progressed my ideas on this subject and, while I've solved my immediate problems by directly editing your database using a simple scripted SQL stream rather than a CVS file, I believe I may be able to be of some use to you.

My thinking now is that MSP should export an API for manipulating the database and perhaps performing other tasks.  My database edits, especially adding new songs, are quite extensive and I'll need to check your schema after every database version change.  An API would present a consistent interface and remove that need and would make user code contributions much simpler; I could easily contribute the CVS merging code without touching your code for instance.  Using an API would also allow other apps to interact with MSP and I'm currently developing one that would benefit from this.  Integration into Tasker would also be possible and would bring MPS into the world of automation.

I worked in the software industry for 24 years and am now working as a musician while dabbling in software tools to make my life easier.  I'm open to collaboration and would happily assist with the design or coding if it would help get the job done. 

Kind regards,
Terry.
Reply
#4
Terry,

Having an API would be wonderful in terms of the contributions MobileSheetsPro users could make to extending the application and even support automation (as you have described). The main difficulty is in figuring out how to handle this well in Android across all supported OS versions (as some are more restrictive than others). I haven't done a lot of research into implementing a plugin-based architecture with an Android application, and the little I've seen points to using services with AIDL. I'm not really sure how well that will fit in with the way MobileSheetsPro works, and my fear is that in trying to support something like that (which would be a considerable amount of work), it could have a negative impact on the application as a whole, as I could introduce bugs or performance issues. The question is how much the majority of users will benefit from being able to add plugins, because I would be spending a lot of time and effort working on that instead of other features which have also been requested. If plugins become commonplace, it also means that users could start encountering bugs and issues due to plugins, but they would come to me for support (greatly increasing the complexity of offering support, which is already a considerable time investment). 

I also would need to see how easy it is to support plugins in a C# UWP application. From what I've seen so far (https://social.msdn.microsoft.com/Forums...=wpdevelop) it points to having to write code to support communication with external applications. So it seems to be similar to Android.

Perhaps if we clearly define what should be possible through IPC with an external application, it may be possible to add support for a more limited set of functions related solely to the database. It still would be a large effort I imagine, so I'm not sure where it will fit into the schedule priority wise. It really depends upon how much demand there is for something like this in order for it to be worked before other things that are commonly requested.

Thanks,
Mike
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.