Hi Sherry,
Now that I've turned us around (sorry), I'm not sure if you're asking about OSF or OJS when it comes to the use of SWORD or native. In my pull request here's what I wrote about SWORD vs native...
When Should I Use the Native API vs. the SWORD API?
---------------------------------------------------
The :doc:`sword` is based on a standard, works fine, and is fully supported, but much more development effort has been going into the :doc:`native-api`, which is not based on a standard. It is specific to Dataverse.
SWORD uses XML. The Native API uses JSON.
SWORD only supports a dozen or so operations. The Native API supports many more.
... and I hope that helps a bit. This is in the new FAQ page and I'm happy to fix it up more or review pull requests.
It doesn't really matter if you use SWORD or native. It all comes down to preference. And OJS or OSF could switch from one to another and we may not even notice. Those are two of our oldest integrations so they definitely started with SWORD but I wouldn't be surprised if they call into the native API here and there. In fact, you have to call into the native API to get the value of ":DatasetPublishPopupCustomText".
I just had to check myself but the return code for getting ":DatasetPublishPopupCustomText" is 200 if it exists and 404 if it doesn't. If you add "-i" to curl you can see this:
Thanks for the Word doc. A new issue would be great. I don't think we'll want to simply include a copy of your Word doc in the guides since we try to avoid proprietary formats but from a quick look I can tell there's some great insight in there, which we can weave into the API Guide.
To all, my pull request to make some improvements to the API Guide has been merged (thanks, Mike for catching and fixing so many typos first) but I'm still definitely interested in feedback. Everyone should feel free to open issues to make more improvements in the future:
https://github.com/IQSS/dataverse/issues
I hope this helps,
Phil