#digitalpreservation — Public Fediverse posts

29 billion unique source files. 438 million projects. One open archive. https://archive.softwareheritage.org
#OpenSource #SoftwareHeritage #DigitalPreservation #PublicCode

29 billion unique source files. 438 million projects. One open archive. https://archive.softwareheritage.org
#OpenSource #SoftwareHeritage #DigitalPreservation #PublicCode

Nu ik al weer een tijdje bezig ben met een aanbeveling uit mijn eigen doctoraalscriptie (boek)geschiedenis van bijna veertig jaar geleden, vond ik het tijd om die ongepubliceerde scriptie online ter beschikking te stellen. Maar wat een (digital preservation) avontuur was dat.

#BoekGeschiedenis #BookHistory #DigitalPreservation

https://cannedit.org/blog/van-tasword-naar-joomla

Nu ik al weer een tijdje bezig ben met een aanbeveling uit mijn eigen doctoraalscriptie (boek)geschiedenis van bijna veertig jaar geleden, vond ik het tijd om die ongepubliceerde scriptie online ter beschikking te stellen. Maar wat een (digital preservation) avontuur was dat.

#BoekGeschiedenis #BookHistory #DigitalPreservation

https://cannedit.org/blog/van-tasword-naar-joomla

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ' (hex: 0x27) and double quotes " (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

inFAMOUS 2's UGC shutdown on August 31 means player-created missions disappear forever. The campaign stays, but digital ownership faces a harsh reality. What does this mean for game preservation? https://mediaboxent.com/infamous-2-ugc-shutdown.html?utm_source=mastodon&utm_medium=social&utm_campaign=social

Published with MBX Flow → https://mbxflow.com

#gaming #digitalpreservation #infamous2 #gamepreservation #ugc #MBXFlow

inFAMOUS 2's UGC shutdown on August 31 means player-created missions disappear forever. The campaign stays, but digital ownership faces a harsh reality. What does this mean for game preservation? https://mediaboxent.com/infamous-2-ugc-shutdown.html?utm_source=mastodon&utm_medium=social&utm_campaign=social

Published with MBX Flow → https://mbxflow.com

#gaming #digitalpreservation #infamous2 #gamepreservation #ugc #MBXFlow

inFAMOUS 2's UGC shutdown on August 31 means player-created missions disappear forever. The campaign stays, but digital ownership faces a harsh reality. What does this mean for game preservation? https://mediaboxent.com/infamous-2-ugc-shutdown.html?utm_source=mastodon&utm_medium=social&utm_campaign=social

Published with MBX Flow → https://mbxflow.com

#gaming #digitalpreservation #infamous2 #gamepreservation #ugc #MBXFlow

inFAMOUS 2's UGC shutdown on August 31 means player-created missions disappear forever. The campaign stays, but digital ownership faces a harsh reality. What does this mean for game preservation? https://mediaboxent.com/infamous-2-ugc-shutdown.html?utm_source=mastodon&utm_medium=social&utm_campaign=social

Published with MBX Flow → https://mbxflow.com

#gaming #digitalpreservation #infamous2 #gamepreservation #ugc #MBXFlow

inFAMOUS 2's UGC shutdown on August 31 means player-created missions disappear forever. The campaign stays, but digital ownership faces a harsh reality. What does this mean for game preservation? https://mediaboxent.com/infamous-2-ugc-shutdown.html?utm_source=mastodon&utm_medium=social&utm_campaign=social

Published with MBX Flow → https://mbxflow.com

#gaming #digitalpreservation #infamous2 #gamepreservation #ugc #MBXFlow

Step inside San Francisco's iconic Grace Cathedral like never before – all from your screen! ⛪

Vincent Woo and team captured this stunning historic landmark using cutting-edge Gaussian splatting technology, rendered smoothly on PlayCanvas. It is digital preservation at its absolute finest. 🖥️✨

https://vincentwoo.com/3d/grace_cathedral/

#GaussianSplatting #3DGraphics #DigitalPreservation #PlayCanvas #WebGL

Step inside San Francisco's iconic Grace Cathedral like never before – all from your screen! ⛪

Vincent Woo and team captured this stunning historic landmark using cutting-edge Gaussian splatting technology, rendered smoothly on PlayCanvas. It is digital preservation at its absolute finest. 🖥️✨

https://vincentwoo.com/3d/grace_cathedral/

#GaussianSplatting #3DGraphics #DigitalPreservation #PlayCanvas #WebGL

Step inside San Francisco's iconic Grace Cathedral like never before – all from your screen! ⛪

Vincent Woo and team captured this stunning historic landmark using cutting-edge Gaussian splatting technology, rendered smoothly on PlayCanvas. It is digital preservation at its absolute finest. 🖥️✨

https://vincentwoo.com/3d/grace_cathedral/

#GaussianSplatting #3DGraphics #DigitalPreservation #PlayCanvas #WebGL

Step inside San Francisco's iconic Grace Cathedral like never before – all from your screen! ⛪

Vincent Woo and team captured this stunning historic landmark using cutting-edge Gaussian splatting technology, rendered smoothly on PlayCanvas. It is digital preservation at its absolute finest. 🖥️✨

https://vincentwoo.com/3d/grace_cathedral/

#GaussianSplatting #3DGraphics #DigitalPreservation #PlayCanvas #WebGL

"Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible."

The systems that do that work are either assumed to exist… or invisible in the funding picture entirely.

Our analysis of 87+ data resilience projects: https://investinopen.org/blog/data-resilience-funding-landscape/

#OpenInfrastructure #DataRescue #DigitalPreservation

"Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible."

The systems that do that work are either assumed to exist… or invisible in the funding picture entirely.

Our analysis of 87+ data resilience projects: https://investinopen.org/blog/data-resilience-funding-landscape/

#OpenInfrastructure #DataRescue #DigitalPreservation

"Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible."

The systems that do that work are either assumed to exist… or invisible in the funding picture entirely.

Our analysis of 87+ data resilience projects: https://investinopen.org/blog/data-resilience-funding-landscape/

#OpenInfrastructure #DataRescue #DigitalPreservation

"Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible."

The systems that do that work are either assumed to exist… or invisible in the funding picture entirely.

Our analysis of 87+ data resilience projects: https://investinopen.org/blog/data-resilience-funding-landscape/

#OpenInfrastructure #DataRescue #DigitalPreservation

"Rescued data has to be collected, and then it has to go somewhere; it has to be validated, described, made findable, and kept accessible."

The systems that do that work are either assumed to exist… or invisible in the funding picture entirely.

Our analysis of 87+ data resilience projects: https://investinopen.org/blog/data-resilience-funding-landscape/

#OpenInfrastructure #DataRescue #DigitalPreservation

2️⃣/2️⃣ These documents are preserved in LoCALDig, the California Local Government Documents Collection at @UCBerkeley, a digital archive created in partnership with @internetarchive.

From CEQA planning and BART studies to housing reports and fiscal analyses, the collection preserves the public record that helps explain how California arrived where it is today.

Dig through LoCALDig on the Internet Archive ⤵️
https://archive.org/details/instituteofgovernmentalstudieslibrary

#Environment #PublicPolicy #DigitalPreservation

2️⃣/2️⃣ These documents are preserved in LoCALDig, the California Local Government Documents Collection at @UCBerkeley, a digital archive created in partnership with @internetarchive.

From CEQA planning and BART studies to housing reports and fiscal analyses, the collection preserves the public record that helps explain how California arrived where it is today.

Dig through LoCALDig on the Internet Archive ⤵️
https://archive.org/details/instituteofgovernmentalstudieslibrary

#Environment #PublicPolicy #DigitalPreservation

2️⃣/2️⃣ These documents are preserved in LoCALDig, the California Local Government Documents Collection at @UCBerkeley, a digital archive created in partnership with @internetarchive.

From CEQA planning and BART studies to housing reports and fiscal analyses, the collection preserves the public record that helps explain how California arrived where it is today.

Dig through LoCALDig on the Internet Archive ⤵️
https://archive.org/details/instituteofgovernmentalstudieslibrary

#Environment #PublicPolicy #DigitalPreservation

2️⃣/2️⃣ These documents are preserved in LoCALDig, the California Local Government Documents Collection at @UCBerkeley, a digital archive created in partnership with @internetarchive.

From CEQA planning and BART studies to housing reports and fiscal analyses, the collection preserves the public record that helps explain how California arrived where it is today.

Dig through LoCALDig on the Internet Archive ⤵️
https://archive.org/details/instituteofgovernmentalstudieslibrary

#Environment #PublicPolicy #DigitalPreservation

2️⃣/2️⃣ These documents are preserved in LoCALDig, the California Local Government Documents Collection at @UCBerkeley, a digital archive created in partnership with @internetarchive.

From CEQA planning and BART studies to housing reports and fiscal analyses, the collection preserves the public record that helps explain how California arrived where it is today.

Dig through LoCALDig on the Internet Archive ⤵️
https://archive.org/details/instituteofgovernmentalstudieslibrary

#Environment #PublicPolicy #DigitalPreservation

📢 New #DPClinic!

🌍 How can humanitarian organisations create sustainable digital archives?

Join Flora Chatt (University of Manchester) and the #DPC on 23 July, 14:00–15:00 UTC for an introduction to the new Digital Humanitarian Archives Toolkit.

💬 Explore the toolkit, hear why it was developed, and help shape it with your feedback.

🎟️ Free registration:
https://www.dpconline.org/events/eventdetail/815/-/dpclinic-july-digital-humanitarian-archives-toolkit

#DigitalPreservation #Coalition #DPC #Archives #Humanitarian #DPClinic #digipres #community #JoinUs

📢 New #DPClinic!

🌍 How can humanitarian organisations create sustainable digital archives?

Join Flora Chatt (University of Manchester) and the #DPC on 23 July, 14:00–15:00 UTC for an introduction to the new Digital Humanitarian Archives Toolkit.

💬 Explore the toolkit, hear why it was developed, and help shape it with your feedback.

🎟️ Free registration:
https://www.dpconline.org/events/eventdetail/815/-/dpclinic-july-digital-humanitarian-archives-toolkit

#DigitalPreservation #Coalition #DPC #Archives #Humanitarian #DPClinic #digipres #community #JoinUs

📢 New #DPClinic!

🌍 How can humanitarian organisations create sustainable digital archives?

Join Flora Chatt (University of Manchester) and the #DPC on 23 July, 14:00–15:00 UTC for an introduction to the new Digital Humanitarian Archives Toolkit.

💬 Explore the toolkit, hear why it was developed, and help shape it with your feedback.

🎟️ Free registration:
https://www.dpconline.org/events/eventdetail/815/-/dpclinic-july-digital-humanitarian-archives-toolkit

#DigitalPreservation #Coalition #DPC #Archives #Humanitarian #DPClinic #digipres #community #JoinUs

📢 New #DPClinic!

🌍 How can humanitarian organisations create sustainable digital archives?

Join Flora Chatt (University of Manchester) and the #DPC on 23 July, 14:00–15:00 UTC for an introduction to the new Digital Humanitarian Archives Toolkit.

💬 Explore the toolkit, hear why it was developed, and help shape it with your feedback.

🎟️ Free registration:
https://www.dpconline.org/events/eventdetail/815/-/dpclinic-july-digital-humanitarian-archives-toolkit

#DigitalPreservation #Coalition #DPC #Archives #Humanitarian #DPClinic #digipres #community #JoinUs

Anyone got thoughts/recommendations on the feasibility of setting up 120k URL redirects (301 Moved Permanently) as part of an institutional repository migration?

#DigitalPreservation #WebArchiving

Anyone got thoughts/recommendations on the feasibility of setting up 120k URL redirects (301 Moved Permanently) as part of an institutional repository migration?

#DigitalPreservation #WebArchiving

Anyone got thoughts/recommendations on the feasibility of setting up 120k URL redirects (301 Moved Permanently) as part of an institutional repository migration?

#DigitalPreservation #WebArchiving

Anyone got thoughts/recommendations on the feasibility of setting up 120k URL redirects (301 Moved Permanently) as part of an institutional repository migration?

#DigitalPreservation #WebArchiving

Anyone got thoughts/recommendations on the feasibility of setting up 120k URL redirects (301 Moved Permanently) as part of an institutional repository migration?

#DigitalPreservation #WebArchiving

The Death of Physical Media and the Real Challenges to Software Archiving

https://fed.brid.gy/r/https://hackaday.com/2026/07/13/the-death-of-physical-media-and-the-real-challenges-to-software-archiving/

The Death of Physical Media and the Real Challenges to Software Archiving

https://fed.brid.gy/r/https://hackaday.com/2026/07/13/the-death-of-physical-media-and-the-real-challenges-to-software-archiving/

The Death of Physical Media and the Real Challenges to Software Archiving

https://fed.brid.gy/r/https://hackaday.com/2026/07/13/the-death-of-physical-media-and-the-real-challenges-to-software-archiving/

📖 New on the DPC Blog: What's new in DART 3?

@ntallman from APTrust explores the latest release of DART 3, introducing new community-requested features that support digital preservation workflows, including expanded packaging options, S3 downloads, upload-only jobs, and an easier migration path from DART 2.

Read the guest blog here 👉🏽 https://www.dpconline.org/blog/blog-dart-3-nathan-tallman

#DigitalPreservation #Coalition #DPC #Community #APTrust #DART #BagIt #OpenSource

📖 New on the DPC Blog: What's new in DART 3?

@ntallman from APTrust explores the latest release of DART 3, introducing new community-requested features that support digital preservation workflows, including expanded packaging options, S3 downloads, upload-only jobs, and an easier migration path from DART 2.

Read the guest blog here 👉🏽 https://www.dpconline.org/blog/blog-dart-3-nathan-tallman

#DigitalPreservation #Coalition #DPC #Community #APTrust #DART #BagIt #OpenSource

📖 New on the DPC Blog: What's new in DART 3?

@ntallman from APTrust explores the latest release of DART 3, introducing new community-requested features that support digital preservation workflows, including expanded packaging options, S3 downloads, upload-only jobs, and an easier migration path from DART 2.

Read the guest blog here 👉🏽 https://www.dpconline.org/blog/blog-dart-3-nathan-tallman

#DigitalPreservation #Coalition #DPC #Community #APTrust #DART #BagIt #OpenSource

📖 New on the DPC Blog: What's new in DART 3?

@ntallman from APTrust explores the latest release of DART 3, introducing new community-requested features that support digital preservation workflows, including expanded packaging options, S3 downloads, upload-only jobs, and an easier migration path from DART 2.

Read the guest blog here 👉🏽 https://www.dpconline.org/blog/blog-dart-3-nathan-tallman

#DigitalPreservation #Coalition #DPC #Community #APTrust #DART #BagIt #OpenSource

💡 How do you preserve digital assets and media for the long term, in a world where software is anything but?

#DigitalPreservation #OpenStandards #OpenScholarship #ResearchInfrastructure #Libraries #Archives #DigitalHumanities #Interoperability

💡 How do you preserve digital assets and media for the long term, in a world where software is anything but?

#DigitalPreservation #OpenStandards #OpenScholarship #ResearchInfrastructure #Libraries #Archives #DigitalHumanities #Interoperability

💡 How do you preserve digital assets and media for the long term, in a world where software is anything but?

#DigitalPreservation #OpenStandards #OpenScholarship #ResearchInfrastructure #Libraries #Archives #DigitalHumanities #Interoperability

💡 How do you preserve digital assets and media for the long term, in a world where software is anything but?

#DigitalPreservation #OpenStandards #OpenScholarship #ResearchInfrastructure #Libraries #Archives #DigitalHumanities #Interoperability

💡 How do you preserve digital assets and media for the long term, in a world where software is anything but?

#DigitalPreservation #OpenStandards #OpenScholarship #ResearchInfrastructure #Libraries #Archives #DigitalHumanities #Interoperability

Booksprint mode: activated 📚

DPC's staff William, Garth, Amy and Karyn are spending three days together at the #DPC's Glasgow office working on the next update of the #DigitalPreservation Handbook!

The Handbook brings together good practice and practical tools to help create, manage and preserve digital materials. This Booksprint is a key milestone in its year-long revision.

We can't wait to share what's coming next! https://www.dpconline.org/handbook