search

DOI-USGS / fort-pymdwizard

The MetadataWizard is a useful tool designed to facilitate FGDC metadata creation for spatial and non-spatial data sets. It is a cross-platform desktop application built using an open-source Python architecture.
https://usgs.github.io/fort-pymdwizard/
Other
62 stars 21 forks source link

Installation error #144

Closed ksnow-usgs closed 2 years ago

ksnow-usgs commented 2 years ago

Looks like the 2.0.7 installer tries to place the start menu shortcut in the ProgramData path instead of the user profile path, which results in an error.

Screenshot image

Desktop

dignizio-usgs commented 2 years ago

@ksnow-usgs - can you confirm whether this error is seen when the install is performed with an elevated (PR) account? It appears some USGS settings may have changed which require elevation for full install. Documentation has been updated for 2.0.7 to reflect the requirement. Please let Kyle (@ennsk) know if you still run encounter the issue after PR install.

ksnow-usgs commented 2 years ago

No error when installing as admin. Installs to C:\Program Files\MetadataWizard. Desktop shortcut created in C:\Users\Public\Desktop. Start Menu shortcut in C:\ProgramData\Microsoft\Windows\Start Menu\Programs. If I recall correctly, the previous version would install everything under the user profile regardless of privilege level.

Installing this with my regular account, it installs to C:\Users\ksnow\AppData\Local\Programs\MetadataWizard. Desktop and start menu shortcuts attempt to install in the same directories as above so don't end up installed, but the program itself runs fine as far as I can tell. Just not very end user friendly since they'd have to figure out where to find the program launcher.

If it's possible to change the shortcut paths to %APPDATA%\Microsoft\Windows\Start Menu\Programs and %USERPROFILE%\Desktop instead of under %PROGRAMDATA% and "%PUBLIC%, then I think anyone would be able to install for themselves like before. If that's the desired behavior. The way it is now I'd probably just create a SCCM/MECM package to push it out for anyone here who wanted the update.

dignizio-usgs commented 2 years ago

Thanks for the update @ksnow-usgs , glad to hear it worked.