FIZ ISE Research Group<p>Our team member <span class="h-card" translate="no"><a href="https://blog.epoz.org/" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>epoz</span></a></span> presented "Now that we have Large Language Models, are metadata standards still necessary?" at the Autumn School 2025 ‘Modern Stained Glass – Metadata – AI’ at University of Münster, Faculty of Catholic Theology</p><p><a href="https://zenodo.org/records/17151141" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">zenodo.org/records/17151141</span><span class="invisible"></span></a></p><p><a href="https://sigmoid.social/tags/llms" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>llms</span></a> <a href="https://sigmoid.social/tags/generativeAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>generativeAI</span></a> <a href="https://sigmoid.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> <a href="https://sigmoid.social/tags/iconclass" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iconclass</span></a> <a href="https://sigmoid.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://sigmoid.social/tags/arthistory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arthistory</span></a> <a href="https://sigmoid.social/tags/dh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dh</span></a> <a href="https://sigmoid.social/tags/digitalhumanities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>digitalhumanities</span></a> <a href="https://sigmoid.social/tags/culturalheritage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>culturalheritage</span></a> <a href="https://sigmoid.social/tags/elephant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elephant</span></a> <a href="https://sigmoid.social/tags/chatgpt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatgpt</span></a> <span class="h-card" translate="no"><a href="https://wisskomm.social/@fiz_karlsruhe" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fiz_karlsruhe</span></a></span> <span class="h-card" translate="no"><a href="https://nfdi.social/@nfdi4culture" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nfdi4culture</span></a></span> <span class="h-card" translate="no"><a href="https://nfdi.social/@NFDI4Memory" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>NFDI4Memory</span></a></span></p>
toot.wales is one of the many independent Mastodon servers you can use to participate in the fediverse.
We are the Open Social network for Wales and the Welsh, at home and abroad! Y rhwydwaith cymdeithasol annibynnol i Gymru, wedi'i bweru gan Mastodon!
Administered by:
Server stats:
624active users
toot.wales: About · Status · Profiles directory · Privacy policy · Terms of service
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.4
#metadata
7 posts · 7 participants · 0 posts today
🌱🏴🅰️🏳️⚧️🐧📎 Ambiyelp<p><span class="h-card" translate="no"><a href="https://hub.workersofthe.world/channel/ferret" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ferret</span></a></span> <a href="https://veganism.social/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a> is centralised and was attempted backdoored by the <a href="https://veganism.social/tags/UnitedKingdom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnitedKingdom</span></a> <a href="https://veganism.social/tags/OnlineSafetyAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OnlineSafetyAct</span></a> and saved by signal threatening to walk. <a href="https://veganism.social/tags/Matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Matrix</span></a> *is decentralised but no <a href="https://veganism.social/tags/QuantumResistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QuantumResistant</span></a> <a href="https://veganism.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>e2ee</span></a> like signal nor its <a href="https://veganism.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> <a href="https://veganism.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> or secret group chats. SimpleX has both and more. more <a href="https://veganism.social/tags/decentralised" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decentralised</span></a> than matrix. quantum-resistant e2ee, metadata privacy, ip protection, <a href="https://veganism.social/tags/tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tor</span></a> support, no persistent id basically "a burner phone for every contact" dms need invites so less dm flooding than matrix<br>Signals centralisation also makes it more vulnerable to total <a href="https://veganism.social/tags/censorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>censorship</span></a> all you need to do is block signals domains, being a decentralised network SimplexChat has no single point of failure to censor and anyone can run their own relay node<br>(ive heard its much easier than matrix homeservers)</p>
Crossref<p>Final call! Abstract submissions close soon. Join us at the Annual Meeting & Board Election as we celebrate 25 years of community and <a href="https://mastodon.online/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> milestones. <a href="https://bit.ly/Crossref2025-CFA" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/Crossref2025-CFA</span><span class="invisible"></span></a></p>
AskUbuntu<p>Metadata Orientatation Unexpected Terminal Results <a href="https://ubuntu.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> <a href="https://ubuntu.social/tags/orientation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>orientation</span></a> <a href="https://ubuntu.social/tags/exiftool" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exiftool</span></a></p><p><a href="https://askubuntu.com/q/1556259/612" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">askubuntu.com/q/1556259/612</span><span class="invisible"></span></a></p>
Mathis<p>Ich bin gerade etwas ratlos - weiß jemand eine gute Möglichkeit, um <a href="https://norden.social/tags/Metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Metadata</span></a> von <a href="https://norden.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forgejo</span></a>-Repos zu sichern? Als <a href="https://norden.social/tags/Backup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Backup</span></a>, mit <a href="https://norden.social/tags/Restore" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Restore</span></a>-Möglichkeit?</p><p>Beim Umstieg auf <a href="https://norden.social/tags/Codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Codeberg</span></a> baue ich logischerweise auch die Lösung mit um, die bisher alle Github-Repos gesichert hat. Der Repo-Inhalt ist mit der API kein Problem: alle Repos des Benutzers holen -> alles klonen bzw. pullen wenn schon da.<br>Die Metadaten fehlen noch, da scheint es leider kein so schönes Tool wie für GH zu geben.</p><p>1/2</p>
Steinar Bangs blogg<p><strong>version control of /etc with git and git-store-meta</strong></p><p> This blog post describes how to use <a href="https://git-scm.com" rel="nofollow noopener" target="_blank">git</a> together with <a href="https://github.com/danny0838/git-store-meta" rel="nofollow noopener" target="_blank">git-store-meta</a> to version control config files in unix/linux <code>/etc</code> directories </p> <p><strong>Intro and backstory</strong></p> <p> I have used <a href="https://en.wikipedia.org/wiki/Version_control" rel="nofollow noopener" target="_blank">version control</a> on the config files in my unix/linux home directories, since the early 90-ies, and used version control on config files in the <code>/etc</code> directory tree of my linux boxes, since I first started setting up linux boxes in the mid-late ninties. </p><p> Initially I used <a href="https://en.wikipedia.org/wiki/Revision_Control_System" rel="nofollow noopener" target="_blank">RCS</a> both for home directory version control. </p><p> But while <a href="https://en.wikipedia.org/wiki/Hidden_file_and_hidden_directory" rel="nofollow noopener" target="_blank">dotfile</a> version control in my home directories transitioned from <a href="https://en.wikipedia.org/wiki/Revision_Control_System" rel="nofollow noopener" target="_blank">RCS</a> controlled files in home directories on various computers, to a shared <a href="https://en.wikipedia.org/wiki/Concurrent_Versions_System" rel="nofollow noopener" target="_blank">CVS</a> repository used in all home directories, which was later transformed from CVS to <a href="https://en.wikipedia.org/wiki/Apache_Subversion" rel="nofollow noopener" target="_blank">SVN</a>, until it was finally converted from SVN to <a href="https://git-scm.com" rel="nofollow noopener" target="_blank">git</a> in May 2011, I continued to use RCS versioning for files in <code>/etc</code> directories on various computers. </p><p> The reason for staying with <a href="https://en.wikipedia.org/wiki/Revision_Control_System#Behavior" rel="nofollow noopener" target="_blank">RCS</a> version control for files in <code>/etc</code> directories was git’s lack of metadata storage, in particular user and group membership and user and group access to files, as well as limiting public access to files. </p><p> To some extent this was handled by RCS (e.g. by giving the version control file the same owner and group membership as the target file), but it always required a bit of manual fiddeling when things broke. </p><p> This blog post explains how to version control <code>/etc</code> directories by combining <a href="https://git-scm.com" rel="nofollow noopener" target="_blank">git</a> with <a href="https://github.com/danny0838/git-store-meta" rel="nofollow noopener" target="_blank">git-store-meta</a> to preserve user and group membership of the versioned files as well as access privileges to the files and even preserve the time of the last change to the files. </p> <p><strong>How to set up version control of /etc directories</strong></p> <p> The first thing to do is to install the prerequisites. On a debian (or ubuntu) system that could be done by doing the following commands as root: </p><p><em></em></p><pre>apt updateapt install git perl</pre><p> Clone the git-store-meta git repository (this can be done by any user. Doesn’t need root privileges): </p><p><em></em></p><pre>cd /tmpgit clone https://github.com/danny0838/git-store-meta.git</pre><p> Then create an empty git repository in the /etc directory. Do the following commands as root </p><p><em></em></p><pre>cd /etcgit --init</pre><p> Rename the default branch (typically <code>master</code> or <code>main</code>) to a branch name reflecting the hostname of the machine containing the <code>/etc</code> directory being versioned, e.g. if the host is named <code>doohan</code>, the branch should be named something like <code>etc-doohan</code>: </p><p><em></em></p><pre>git branch -M master etc-doohan</pre><p> Add an <code>/etc/.gitignore</code> file ignoring everything (which means that version control of new files has to be done by forcibly adding the files with “<code>git add -f</code>“): </p><p><em></em></p><pre>cd /etcecho "*" >.gitignoregit add -f .gitignoregit commit -m "Ignore all unknown files found in /etc and subdirectories"</pre><p> Copy git-store-meta into the git repository of <code>/etc/.git</code> and create an initial metadata file with the necessary fields for controlling and versioning ownership and access of files in <code>/etc</code> </p><p><em></em></p><pre>cd /etccp /tmp/git-store-meta/git-store-meta.pl .git/hooks/.git/hooks/git-store-meta.pl --store -f user,group,mode,mtime,atimegit add -f .git_store_metagit commit -m "Add git-store-meta metadata file"</pre><p> Set up the git-store-metadata hooks which will update <code>.git_store_meta</code> on commits and add <code>.git_store_meta</code> to the commit and will set metadata values on files when updating a branch: </p><p><em></em></p><pre>cd /etc.git/hooks/git-store-meta.pl --install</pre><p> Add a remote (make sure it is not a public repository) and push the branch: </p><p><em></em></p><pre>git remote add origin git@git.example.com:~exampleuser/etc-configgit push -u origin HEAD</pre> <p><strong>Using git version control of /etc for a new file</strong></p> <p> In the future, when doing changes to a new config file, do the following: </p><ol><li><p> Add the current version of the file to git (the “-f” flag is necessary because of the .gitignore file excluding all files by default) </p><p><em></em></p><pre>cd /etcgit add -f dnsmasq.confgit commit -m "Add version of dnsmasq.con distributed by debian 13 trixie"</pre></li><li><p> Make local modifications to the configuration files and commit the changes and push the branch to the remote for safekeeping </p><p><em></em></p><pre>cd /etcgit add dnsmasq.confgit commit -m "Adapt dnsmasq to home network"git push</pre><p> (note that the “-f” flag isn’t necessary on “git add” here) </p></li></ol> <p><strong>Preserving history from RCS files</strong></p> <p> When adding git versioning to <code>/etc</code> I preserved the history from existing the RCS version control files on the various computers, by </p><ol><li><p> Creating a CVS repository based on RCS files from <code>/etc</code> </p><p><em></em></p><pre>mkdir /tmp/etc-cvscd /etcfind . -name RCS | xargs tar cf - | (cd /tmp/etc-cvs; tar xf -)</pre></li><li><p> installed <a href="https://gitlab.com/esr/cvs-fast-export" rel="nofollow noopener" target="_blank">cvs-fast-export</a> on the computer where the conversion was run (must be done by root or sudo) </p><p><em></em></p><pre>apt install cvs-fast-export</pre></li><li><p> exported the cvs repo to a fast-import file and then imported that file into an empty git repository </p><p><em></em></p><pre>cd /tmp/etc-cvs/find -type f | cvs-fast-export >/tmp/etc.dumpmkdir /tmp/etc-configgit initgit fast-import </tmp/etc.dumpgit branch -m master etc-doohangit config user.name "root doohan"</pre></li><li><p> moved the new .git directory to <code>/etc</code> </p><p><em></em></p><pre>cd /etcmv /tmp/etc-config/.git .</pre></li><li>then added git-store-meta metadata versioning and pushed the branch to a remote, as outlined in the previous section</li></ol> <p><strong>Closing words</strong></p> <p> I also added git-store-meta metadata versionining to git versioning of my various home directories, which removed the need to manually do “<code>chmod go-rwx</code>” on files that should be unaccessible to others after switching branches or merging branches. </p><p> When I first looked into using git for <code>/etc</code> version control, back in 2018, I had planned to use a tool named <a href="https://github.com/przemoc/metastore" rel="nofollow noopener" target="_blank">metastore</a> to store the metadata of <code>/etc</code> directory. </p><p> However, metastore proved to be unsatisfactory for adding metadata support to git: </p><ol><li>metastore added metadata for all files in the <code>/etc</code> directories and subdirectories, not just the files version controlled by git, which caused git updates and commits to become very slow</li><li>metastore metadata files were binary, which isn’t optimal for git versioning of the files or visual inspection of commits</li><li>the last commit was from February 1 2023, which isn’t too long ago, but the last release of metastore was version 1.1.2 on January 6 2018, which <i>is</i> a long time ago</li></ol><p> In contrast <a href="https://github.com/danny0838/git-store-meta" rel="nofollow noopener" target="_blank">git-store-meta</a> has can be used from its main HEAD, rather than a specific release, was easy to install, only tracked metadata for files in git in a human readable <a href="https://en.wikipedia.org/wiki/Comma-separated_values" rel="nofollow noopener" target="_blank">CSV</a> file, and worked well (i.e. does what it is supposed to do without breaking anything in the process). </p> <p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/config/" target="_blank">#config</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/configfiles/" target="_blank">#configfiles</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/cvs/" target="_blank">#cvs</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/etcdir/" target="_blank">#etcdir</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/git/" target="_blank">#git</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/gitstoremeta/" target="_blank">#gitstoremeta</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/metadata/" target="_blank">#metadata</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/rcs/" target="_blank">#rcs</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://steinar.bang.priv.no/tag/svn/" target="_blank">#svn</a></p>
Crossref<p>We're looking for a Technical Support Specialist to join our Membership team!</p><p>Remote, full-time, and focused on helping our global community use metadata to support open research.</p><p>Applications open now.</p><p>Details: <a href="https://tinyurl.com/395yhtr5" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tinyurl.com/395yhtr5</span><span class="invisible"></span></a> </p><p><a href="https://mastodon.online/tags/hiring" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hiring</span></a> <a href="https://mastodon.online/tags/openscience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openscience</span></a> <a href="https://mastodon.online/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> <a href="https://mastodon.online/tags/jobs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jobs</span></a> <a href="https://mastodon.online/tags/remote" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>remote</span></a></p>
Crossref<p>CALL FOR ABSTRACTS––Got a <a href="https://mastodon.online/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> story, case study, or insight to share? Flash talks and posters are part of our Annual Meeting and Board Election. Submit by 20 Sept. All languages welcome! <a href="https://bit.ly/Crossref2025-CFA" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/Crossref2025-CFA</span><span class="invisible"></span></a></p>
Donald Hobern<p>A Strategic Community <a href="https://scicomm.xyz/tags/Roadmap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Roadmap</span></a> for an <a href="https://scicomm.xyz/tags/Australian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Australian</span></a> <a href="https://scicomm.xyz/tags/FAIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FAIR</span></a> <a href="https://scicomm.xyz/tags/Vocabulary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vocabulary</span></a> Ecosystem</p><p><a href="https://doi.org/10.25911/N6K8-F540" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">doi.org/10.25911/N6K8-F540</span><span class="invisible"></span></a></p><p>Three years ago, I participated in a very engaged workshop at <a href="https://scicomm.xyz/tags/ANU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ANU</span></a> on <a href="https://scicomm.xyz/tags/vocabularies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vocabularies</span></a> for FAIR <a href="https://scicomm.xyz/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>data</span></a> management. It sharpened how I think about vocabularies. I now see them primarily as a <a href="https://scicomm.xyz/tags/KnowledgeTransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KnowledgeTransfer</span></a> tool for representing domain expertise in an actionable form. And I think we do a terrible job both at highlighting how critical they are (particularly in an age where trusted expertise is harder to find) and also at making them easier for others to find and reuse.</p><p>I picture this scenario. A student is about to start collecting data for their thesis. They need to make choices about what variables to observe or what questions to ask participants, and they need to think about how they want to represent the results to support their analysis. In the ideal case, the actual data collecting effort is about populating an imagined but initially empty data matrix. If they could be assisted to find the best structured and most widely used (in their domain) vocabularies for any categorical values in their data, it would be possible to generate that template matrix with in-built validation tools, etc. The data they finally collect would have most of its metadata already defined and would be properly interoperable with data collected by others in their domain. Meta-analysis would be much simpler.</p><p>I am interested in why tools like this don't really exist, or at least why they are not mainstream. I think it's because vocabularies are seen as such an ultra-nerdy subset of the nerdy topic of <a href="https://scicomm.xyz/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> rather than presented as an opportunity to stand on the shoulders of others. What can be done to make them more friendly and intuitive for such purposes?</p><p>Finally, after way too many struggles, we have a report and recommendations from from that meeting in 2022. I tried to add some of these ideas to the final product as best I could.</p>
artun<p><a href="https://mastodon.world/tags/Metanarratives" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Metanarratives</span></a> and <a href="https://mastodon.world/tags/epistemologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>epistemologies</span></a> are scaffolds, structures, a type of <a href="https://mastodon.world/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a>, in which <a href="https://mastodon.world/tags/knowledge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>knowledge</span></a> lives and breaths or suffocates or misinforms or enlightens and inspires.</p><p>Choosing our metanarratives critically, and in ways informed historically and by unpacking various forms of <a href="https://mastodon.world/tags/power" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>power</span></a> and <a href="https://mastodon.world/tags/politics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>politics</span></a>, is vital, for people, communities, institutions, countries, social justice and the <a href="https://mastodon.world/tags/planet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>planet</span></a>.</p><p>Thinking of <a href="https://mastodon.world/tags/epistemologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>epistemologies</span></a> before knowledge.</p><p><a href="https://mastodon.world/tags/arts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arts</span></a> <a href="https://mastodon.world/tags/sciences" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sciences</span></a> <a href="https://mastodon.world/tags/creativity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>creativity</span></a> <a href="https://mastodon.world/tags/criticalepistemology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>criticalepistemology</span></a></p>
Steffi Genderjahn<p>👀 One year after the introduction of Grant DOIs at the Dutch Research Council <a href="https://openbiblio.social/tags/NWO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NWO</span></a> </p><p>👉 <a href="https://doi.org/10.64000/dvqke-j4v69" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">doi.org/10.64000/dvqke-j4v69</span><span class="invisible"></span></a></p><p>Important aspects:<br>🟣 Researchers are implementing the use of Grant <a href="https://openbiblio.social/tags/DOIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DOIs</span></a> well<br>🟣 Publishers should work on better capturing and processing <a href="https://openbiblio.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> on funding <br>🟣 Older projects do not yet have DOIs</p><p>Grant DOIs advance open, connected science, with funders, researchers, and publishers all sharing the role to unlock the full potential of <a href="https://openbiblio.social/tags/openresearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openresearch</span></a> data.</p><p><a href="https://openbiblio.social/tags/OpenScience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenScience</span></a> <a href="https://openbiblio.social/tags/PIDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PIDs</span></a> <span class="h-card" translate="no"><a href="https://mastodon.online/@crossref" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>crossref</span></a></span></p>
Serhii Nazarovets<p>GAIDeT has grown beyond a simple disclosure format - it now exists as a formal RDF/OWL ontology. This makes AI-use declarations machine-readable and ready for integration into <span class="h-card" translate="no"><a href="https://mastodon.online/@crossref" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>crossref</span></a></span> metadata. </p><p>To help editors, repositories & librarians: we’ve published a full instruction with <a href="https://mstdn.science/tags/XML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XML</span></a> snippets & Web Deposit Form examples:</p><p>👉 <a href="https://doi.org/10.5281/zenodo.17101228" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">doi.org/10.5281/zenodo.17101228</span><span class="invisible"></span></a> </p><p><a href="https://mstdn.science/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://mstdn.science/tags/GenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenAI</span></a> <a href="https://mstdn.science/tags/EthicalAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EthicalAI</span></a> <a href="https://mstdn.science/tags/Transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Transparency</span></a> <a href="https://mstdn.science/tags/GAIDeT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAIDeT</span></a> <a href="https://mstdn.science/tags/OpenScience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenScience</span></a> <a href="https://mstdn.science/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLM</span></a> <a href="https://mstdn.science/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a></p>
AskUbuntu<p>Music files not displaying album art <a href="https://ubuntu.social/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> <a href="https://ubuntu.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a></p><p><a href="https://askubuntu.com/q/1555934/612" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">askubuntu.com/q/1555934/612</span><span class="invisible"></span></a></p>
PID Network Deutschland<p>At <a href="https://openbiblio.social/tags/CoRDI2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CoRDI2025</span></a>, we saw how <a href="https://openbiblio.social/tags/PIDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PIDs</span></a> make research more visible and <a href="https://openbiblio.social/tags/FAIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FAIR</span></a>. At our poster, we spoke with many members of the <a href="https://openbiblio.social/tags/RDM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDM</span></a> community about the relevance of PIDs and the interoperability of <a href="https://openbiblio.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a> for sustainable <a href="https://openbiblio.social/tags/OpenScience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenScience</span></a> in Germany.</p><p>The poster is now also available on Zenodo! 🥳 </p><p>👉 <a href="https://doi.org/10.5281/zenodo.16636357" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">doi.org/10.5281/zenodo.16636357</span><span class="invisible"></span></a> 💫</p><p><a href="https://openbiblio.social/tags/NFDI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NFDI</span></a> <a href="https://openbiblio.social/tags/PIDNetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PIDNetwork</span></a> <span class="h-card" translate="no"><a href="https://nfdi.social/@NFDI" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>NFDI</span></a></span> <span class="h-card" translate="no"><a href="https://nfdi.social/@pid4nfdi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pid4nfdi</span></a></span></p>
ChadF :pci:<p><a href="https://podcastindex.social/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>metadata</span></a></p><p>Had a chat with <span class="h-card" translate="no"><a href="https://podcastindex.social/@merryoscar" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>merryoscar</span></a></span> last night about this Nostr and metadata stuff and I realized what the real probably is. Metadata has always been broken. </p><p>We have always had Helipad on nodes and any other alternatives has always fallen short. Fountain, Alby dashboard, Satoshi.stream (maybe?), Wavlake app and site. </p><p>If you've always used Helipad you don't know this problem exist. I've heard <span class="h-card" translate="no"><a href="https://podcastindex.social/@mikeneumann" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mikeneumann</span></a></span> and <span class="h-card" translate="no"><a href="https://podcastindex.social/@sirtjthewrathful" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sirtjthewrathful</span></a></span> talk about this a lot.</p>
Replied in thread
@pneutig @chlobemy @edri “We kill people based on metadata.”
– Former Director of the NSA and CIA, General Michael Hayden
https://www.justsecurity.org/10318/video-clip-director-nsa-cia-we-kill-people-based-metadata/
Just Security · Video Clip of Former Director of NSA and CIA: “We Kill People Based on Metadata”In a public debate with Just Security‘s David Cole at Johns Hopkins University, former Director of the NSA and CIA, General Michael Hayden made the provocative remark, “We Kill People Based on Metadata.” In a post on Saturday, David used Gen. Hayden’s statement as a pivot to discuss shortcomings in current congressional efforts to reform the NSA’s metadata […]
New abstract from #Munin2025! 
Accessibility Metadata: Making Accessible Content in Repositories Discoverable by Maria Guseva.
Ensuring barrier-free science starts with making accessible content findable.
https://doi.org/10.7557/5.8187
doi.orgAccessibility Metadata: Making accessible content in repositories discoverable
| Septentrio Conference Series
Key issues with XChat (X’s new encrypted‑chat feature)
Metadata leakage – Images sent through XChat keep EXIF data (e.g., GPS coordinates), so location information can be exposed even though the chat is encrypted.
Server‑stored keys – Private encryption keys are kept on X’s servers and protected only by a four‑digit PIN. This means the service (or a malicious insider) could retrieve the keys and read users’ messages.
Lack of open‑source code – The implementation isn’t publicly auditable, preventing independent verification that the encryption truly works as advertised.
Missing perfect‑forward‑secrecy – Compromise of a single key would give an attacker access to all past and future messages; XChat currently lacks robust forward‑secrecy mechanisms.
https://san.com/cc/not-so-secret-xs-new-encrypted-chat-feature-puts-users-at-risk-experts-say/ ( summarized by https://lumo.proton.me )
Straight Arrow NewsNot so secret: X’s new encrypted chat feature puts users at risk, experts sayX's new XChat feature does not remove sensitive metadata from images, which could lead to the exposure of GPS coordinates.
Discover PKP + #SFU Master of #Publishing (MPub) new #OpenPublishing course: Technologies & Infrastructure (PUB 604)
practical training with #OpenJournalSystems #OJS & scholarly Application Programming Interfaces #APIs content management systems #metadata standards #DigitalPreservation techniques #OpenAccess & #OpenSource technologies role of #libraries & repositories
Chance for discount & learn more:
https://pkp.sfu.ca/2025/08/22/sneak-peek-at-pkp-sfu-new-open-publishing-series/
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload