Hi Nathanael,
This is a known issue, with a simple stop-gap fix added to 2.0.1, and a workaround available. Please see issue
#4247.
At the moment, in 2.0.0, there is no option to select the taxononmy to which you are trying to import via Import > XML. Adding further options to this page, to allow users greater control over their imports, is likely the long-term solution. In the meantime, we added a link to the import page, that redirects users directly to the SKOS import page, where a taxonomy can be selected from a drop-down autocomplete list of available taxonomies. We set the Places taxonomy as the default value on this new page, but a user can delete "Places" from the drop-down list and select a different taxonomy as needed.
Here is the revised Import page, with the link:
When a user clicks on the link, they are redirected to the SKOS import page, where we've added the autocomplete drop-down. The URL for this page (using the demo site as an example):
http://demo.accesstomemory.org/sfSkosPlugin/import
There is also a means in 2.0.0 and earlier of importing terms directly into the target taxonomy - but at the moment, this requires a top-level term to be possible.Navigate to an existing term (Manage > Taxonomies and select a taxonomy, and the select an existing term or create a new one and save - in the right hand context menu, there is a SKOS import option that will bring in terms as children of the current term). However, this means that, as a quick workaround, you could create a discardable top-level place term, import your taxonomy as children, and then delete the top-level term.
Note that the Vagrant box is intended primarily for developers interested in working with the application, who would like to test locally - so while it is possible to update the box (via a git pull --rebase, sql upgrade, restart of php services, and repopulation of the search index), it can be complicated, and doing so will pull in all changes from our development branch. While I don't recommend this practice for users who are not experienced with command-line operations and use of git, I do hope to add developer instructions for doing so to our documentation in the near future.
Regards,