#dataverse
These are public posts tagged with #dataverse. You can interact with them if you have an account anywhere in the fediverse.
Our NFDI4Cat Repository has been accepted into the 4th NFDI AII Incubator Cycle!
We'll explore integrating NFDI AAI for seamless and secure access to our Dataverse-based research data platform.
Looking forward to collaborating with IAM4NFDI and the community!
Incubator: https://incubators.nfdi-aai.de
Repository: https://data.nfdi4cat.org
Day 2 of the Ready for BioData Management Intensive Course just wrapped up at CIIMAR!
Hands-on sessions with #Galaxy, #Dataverse & the Data Stewardship Wizard helped bring #RDM and #FAIRdata to life.
Thanks to all who joined us!
July 2nd, 2015 - the first DOI was assigned to a dataset in our research data repository RepOD 
https://repod.icm.edu.pl/
Today we host almost 60 institutional dataverses and over 2 600 datasets.
You can read more about RepOD here: https://info.repod.icm.edu.pl/?page_id=56&lang=en
#repositories #RDM #openscience #researchdata #dataverse #academia #research
In late 2024, we launched a collaboration between The Carpentries and the Generalist Repository Ecosystem Initiative (GREI), aiming to explore how generalist data repositories such as #Dataverse, #Dryad, #Figshare, Mendeley Data, Open Science Framework, #Vivli, and #Zenodo might be more intentionally woven into the data skills we teach. 
In the process, we also asked ourselves some important questions: 
What would it look like if open data repositories weren’t just add-ons at the end of a workflow, but upfront teaching concepts in our lessons? How can we position generalist repositories as active components in retrieving and processing datasets? How can we give researchers the tools not just to write clean code, but to publish their work in ways that make it reusable and citable by others?
Learn about the important steps we have taken in this collaboration toward co-creating new lesson content: https://carpentries.org/blog/2025/06/update-on-the-carpentries-and-grei-collaboration/ 
In late 2024, we launched a collaboration between The…
The Carpentries5. The next SharePoint? If we'd only look at what's the data source for canvas apps out there, #Dataverse is nowhere near #SharePoint. Yet the more MS is aiming for an agentic future of work, the bigger the demand for a platform that could orchestrate such human-AI collaboration. I expect Dataverse to have a growing footprint here.
4. Common currency for SaaS analytics consumption. Surprisingly, the #Dataverse database storage is now used for paying not just for operational business application capacity. It also extends to #MicrosoftFabric services that remove the need for Azure resources.
2. Governance toolkit for IT admins. No matter how the in-product features improve, practical governance of apps, flows and now agents still often requires customer specific activities - faciliated by #Dataverse and the growing number of 'Kits.
3. DevOps backbone for solution developers. Git integration and Power Platform Pipelines deliver built-in tooling that makes proper ALM accessible to a far broader audience than the earlier pro-dev driven custom pipelines.
After posting about the history of Microsoft #Dataverse last week, time to go back to the future. How is it used today in #PowerPlatform and beyond? I thought about it for a while and saw myself write about these 5 use cases.
1. "Enterprise data platform for #copilot ": The official MS marketing pitch, which bends the truth in usual ways, but is still partially correct. It would be more accurate if they left the "data" part away.
Hi folks, #Dataverse is new at MPOW and I have a question.
As it's set up now, at least, PDF previews in Yale Dataverse are set up such that you see the top of the page, scroll down to read the bottom of the page, and then click a "next" button to get to the next page. Not very convenient.
OSF and Zenodo both have preview viewers where PDFs can be scrolled through.
Is this something special about how Dataverse is set up here? Or is that just the way it is?
Microsoft announced "real-time data warehousing with Microsoft Dataverse and Fabric zero-copy integration". Which is cool.
Now, just because there is "no ETL, no data copy", that doesn't mean you wouldn't be charged for storage capacity.
If this is paid with #Dataverse DB capacity, the cost is 260x higher than raw OneLake storage.
Suddenly the turnkey SaaS option ain't so cheap.
More thoughts on LI: https://www.linkedin.com/feed/update/urn:li:share:7312740000025010176/
Recently I uploaded over 35k files into a #Dataverse dataset. I simply forgot to check the data the researcher handed me over. Software is extremely unhappy.
JSON info about it is 40 MB. jq filtered me the file IDs quickly and now a shell script is deleting the files. One by one. 15 seconds each. That will take a while.
Power Apps are meant for you internal user audience. What can we do to expose Dataverse data to external users like customers?
#PowerPages isn't the only option that customers should explore. In fact, even portals/websites aren't alwaysthe best tool.
In my Perspectives on #PowerPlatform newsletter, I present both traditional and creative ways to allow external users to interact with data in your #Dataverse environment: https://www.perspectives.plus/p/external-access-to-power-platform-data
Even when they DO ship the features, nothing gets reflected on the idea sites. Here's one example of ideas on #Dataverse storage mgmt on environment level.
It was shipped, and we almost didn't notice. All those ideas remain in "new" status.
More thoughts here: https://www.perspectives.plus/p/product-ideas-in-the-void
48th institutional dataverse in the Repository for Open Data RepOD has just been published https://repod.icm.edu.pl/dataverse/ujk Jan Kochanowski University of Kielce
See, explore and browse all dataverses & research data in RepOD 
https://info.repod.icm.edu.pl/?page_id=593&lang=en
Git isn't only for people who write code. The new native #Dataverse Git integration shows the value of automated version control.
For as long as I remember, I've wished there was a built-in version history in Dataverse. No, not the audit history for data. The changes performed on metadata. Who changed what and when?
Now, together with #AzureDevOps, we have a change log for #PowerPlatform solutions and environments. (In preview.)
More thoughts in my newsletter: https://www.perspectives.plus/p/gotta-git-with-the-times
Writing about the new #Dataverse Git integration for my next week's newsletter, I got the opportunity to re-use this #lowcode meme pic I made a few years ago about #PowerApps citizen devs vs. oldskool XRM devs.
Subscribe and get the article to your inbox once it's ready: https://www.perspectives.plus/
Don't even bother with the #PowerPlatform Admin Center security role editor anymore.
Use this new _n.RoleEditor in #XrmToolBox, to see 33 rows instead of 3 in one screen. Plus tons of powerful features for viewing and editing the intricate details of #Dataverse security model.
#RDM #IRD #joboffer #Dataverse
Un poste d'administrateur de portail de données de la recherche à Montpellier, à l'IRD
https://emploi-recrutement.ird.fr/offre-de-emploi/emploi-administrateur-de-datasuds-entrepot-des-donnees-de-la-recherche-f-h_213.aspx
Nice to see new #Dataverse storage capacity allocation tools being rolled out in #PowerPlatform admin center. At least guarding these scarce (read: expensive AF) resources is now a bit easier for #lowcode platform admins.
See this post on LI for more thoughts: https://www.linkedin.com/feed/update/urn:li:activity:7247870527933997057/
Been aware of Mark Carrington's excellent SQL4CDS tool for a while but not used it much. The recent optional integration with an OpenAI CoPilot will probably make all the difference for occasional SQL users such as myself.
https://www.synesthesia.co.uk/stream/bookmark-of-sql-4-cds-xrmtoolbox-tool-mark-carrington/
I’ve been aware of this clever tool from Mark Carrington…
www.synesthesia.co.uk