08-27-2024, 05:49 AM
This is the logic for how the import works (assuming MobileSheets is managing the files which is a setting that is only available on Android):
1) A PDF is selected and imported
2) A title for the new song has to be determined, which is calculated based on whether PDF metadata is being extracted (and with the next update, is being used for the title), or the dropdown selection on the import dialog
3) If "Create Subdirectory per Song" is enabled, a folder will be created in the storage location that matches the calculated title for the song.
4) The output location for the file is calculated based on #3 plus the storage location path + the name of the PDF. So if we are on Windows, for example, no subdirectories are used and the PDF is named "Song 1.pdf", MobileSheets checks C:\Users\<your username>\AppData\Local\Packages\41730Zubersoft.MobileSheets_ys1c8ct2g6ypr\LocalState\Song 1.pdf to see if it already exists (assuming you are using the default storage location)
5) If Song 1.pdf already exists, MobileSheets checks the calculated hash for the existing file against the calculated hash for the new file to see if they match. Any modification, no matter how minor to the PDF, will cause the hash to be different. If the hashes do not match, a conflict dialog is displayed letting the user choose how to handle the new version of the PDF. If a Song 1.pdf does not exist, the new file will just be used and a song will be created with no need for user import. If Song 1.pdf is identical to what is already being used in the library, then it will either be ignored or a new song will be created using the same file based on the duplicate file behavior dropdown
That is the only thing that is considered. The metadata in MobileSheets plays no part. It just matters whether the PDF itself is different from what is already being used.
Mike
1) A PDF is selected and imported
2) A title for the new song has to be determined, which is calculated based on whether PDF metadata is being extracted (and with the next update, is being used for the title), or the dropdown selection on the import dialog
3) If "Create Subdirectory per Song" is enabled, a folder will be created in the storage location that matches the calculated title for the song.
4) The output location for the file is calculated based on #3 plus the storage location path + the name of the PDF. So if we are on Windows, for example, no subdirectories are used and the PDF is named "Song 1.pdf", MobileSheets checks C:\Users\<your username>\AppData\Local\Packages\41730Zubersoft.MobileSheets_ys1c8ct2g6ypr\LocalState\Song 1.pdf to see if it already exists (assuming you are using the default storage location)
5) If Song 1.pdf already exists, MobileSheets checks the calculated hash for the existing file against the calculated hash for the new file to see if they match. Any modification, no matter how minor to the PDF, will cause the hash to be different. If the hashes do not match, a conflict dialog is displayed letting the user choose how to handle the new version of the PDF. If a Song 1.pdf does not exist, the new file will just be used and a song will be created with no need for user import. If Song 1.pdf is identical to what is already being used in the library, then it will either be ignored or a new song will be created using the same file based on the duplicate file behavior dropdown
That is the only thing that is considered. The metadata in MobileSheets plays no part. It just matters whether the PDF itself is different from what is already being used.
Mike