Yes, contact Magnus with requests, will take a little bit of time to write the code but will be quick if available in MARC
Q2: Sorry if I didn't understand correctly, SourceMD would import scientific publications as wikidata items with all core statements?
notetaker did not catch the answer -- group assistance requested!
Q3: Will QuickStatements using CSV be available to bulk create properties for a Wikibase instance?
Magnus did not write the CSV importer, would need to dig into it, on the “to-do” list
C1: putting an authorized access point into the description field doesn't seem terribly helpful or appropriate
Q4: what is your preferred way to be contacted when support is needed, i.e. if a Mix'n'Match catalog has errors and the catalog needs to be refreshed? I've found a few different methods but am never sure what is best to ensure it doesn't slip through.
Q5: What would you suggest to the Wikimedia Foundation to support you and other programmers?
use the tools, pull requests always welcome, if you want to be a co-maintainer on one of my tools, please come forward (even if just to re-start when it breaks down)
support from wikimedia foundation has been good recently
Q6: Question about motivation that spurred Magnus to create so many great tools for the community.
Would start creating tools in response to doing tasks manually and wanting a more efficient way to do it.
mix’n’match (for example) was initially a request from a user to match oxford bio to wikipedia; magnus opted to match to wikidata instead, and lets not limit it just to odbn data!
Q7: Recently we had a speaker who is working on a new API for Wikidata. It seemed nice because it is simpler than the current MediaWiki API. However, it sounded like they were not necessarily supporting all of the features of the current API and that they might deprecate the current API. I found this alarming because it would break so many things if it were true. I assume it would also break many of your tools. Are you concerned about this?
Magnus not currently using the API; once it is in a state that is a s good as the current one, will look into migrating (like to stay on top of tech developments)
wbedit entity will not be going away anytime soon; will likely have both APIs active until the new API becomes more robust and the old API falls out of usage
Comments/discussion from chat
Yes. There is quite a long deprecation period planned. And so far it's not a feature-parity with the action API
Please contact Lydia Pintscher (User:Lydia_Pintscher_(WMDE)) know about things you're missing in the REST API or issues you run into
Comment from chat: I have absolutveryely no plans to port my own tools to the REST API, fwiw
Q8: What are you planning for the future?
Please contact Magnus if you have suggestions or tools you need!