kshepherd

@mwoodiupui that uses SecurityManager under the hood, so it breaks things in the same way. In my PR I circumvented this by rewriting the CLI tools so an `execute` function...

noting that while testing some things out today, only dismax and edismax support `bq` boost queries too (helpful to e.g. boost latest versions of items) i also agree with the...

Digging a bit more into this, jtwig is really old (no updates for 6+ years), it was written by the original XOAI author, so I think one recommendation would be...

@saschaszott agreed, removal of jtwig seems the best way and there are no obvious easy 'workarounds'. I would prefer to leave this ticket open for now, but linked to #10009...

Something else I've noticed about LiveImport, is that the map of "MetadataFieldConfig" causes the *field config* to be a unique key, rather than the reference to the MetadataContributor object*. This...

The legacy (pre DSpace 7) UIs and legacy Java API DescribeStep did use the `default.langauge` property to populate a default language in submission and edit item metadata forms, but it...

@tdonohue Could you please give this a re-review? I have addressed all your feedback, although haven't changed that commented-out field - if you think my answer is not quite satisfactory,...

@tdonohue this should now be ready, all tests are passing. I also updated my documentation at https://github.com/kshepherd/dspace-geospatial-maps-doc/blob/main/README.md to include example formats for bounding box and point data, and the new...

Thanks @toniprieto ! I have addressed the view mode button control flow as you noted, and removed the console output. I agree with you that we should document the implication...

thanks @tdonohue for the extra testing. I'll look into the issues here, but regarding the browse map, I think the discovery rebuild might not be quite enough, as we add...