home.social

#documentmanagement — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #documentmanagement, aggregated by home.social.

  1. 🎉🤖 "Groundbreaking discovery: letting #AI fiddle with your documents results in... corrupted documents! Who knew? 🚀 This revelation is right up there with finding out water is wet, but don't worry, #arXiv is now independent, so at least they've got that going for them. 🙄"
    arxiv.org/abs/2604.15597 #Corruption #Groundbreaking #Discovery #TechNews #DocumentManagement #HackerNews #ngated

  2. Denmark’s central bank picks Tieto for document management

    Danmarks Nationalbank, Denmark’s central bank, has selected Nordic software and services firm Tieto to deliver an Electronic Case…
    #Denmark #Danmark #DK #Europe #Europa #EU #casemanagement #Centralbanking #DanmarksNationalbank #denmark #documentmanagement #financialinfrastructure #Indtech #Nordic #norway #Public360° #regtech #SaaS #scandinavia #sweden #Tieto
    europesays.com/2970272/

  3. 💚 This NEW SharePoint Feature Makes Multi-Step Approvals EASY

    Are you still losing time on manual document approvals? Let SharePoint handle it with ease! 😉 Discover now:

    ✅ How to activate document approval features 🎯
    ✅ Setting up multi-stage processes 🔄
    ✅ Enable dynamic approval routing 🌐
    ✅ Automate Teams notifications 🔔
    ✅ Create flexible approval chains effortlessly 🔗

    Get started on automating your workflows and save time by transitioning from email chases to seamless approvals.

    ▶︎ hubsite365.com/en-ww/pro-offic

    #SharePoint #DocumentManagement #Microsoft365 #ProcessAutomation #QuickSteps

  4. Seamless Document Management with Greenbox + MS Office! 📂

    Now, integrate Greenbox with MS Office for effortless document creation, editing, and collaboration—all in one place! 🔄

    ✅ Edit & save directly from MS Word, Excel, & PowerPoint
    ✅ Streamline workflows & enhance productivity

    Boost efficiency with the perfect duo! Try Greenbox with MS Office today.

    Visit: zurl.co/q4TQL

    #GreenboxDMS #MSOfficeIntegration #SeamlessWorkflow #DocumentManagement #BusinessEfficiency #WorkSmarter

  5. Does anyone have ideas on how to manage, store, and catalog a collection of 300+ screenshots and other documents? It would be really cool if it was FOSS. Bonus points if it allows the public to browse either specific entries or the entire database through a web interface.

    #DataArchival #DataStorage #DataHoarding #DocumentManagement

  6. @JoBlakely It's called "library science".

    And therein lie conflicts, beliefs, irreconcilable differences, religions, and civil wars.

    I'd hashtagged Paul Otlet, who made this his life's work in the early 20th century, culminating in a vast index-card driven database in Belgium, the Mundaneum, ultimately destroyed by the Nazis in WWII.

    en.wikipedia.org/wiki/Paul_Otl

    Amongst bibliographic standards, there's the Dublin Core (named after the city in Ohio, not Ireland), which attempts to describe a set of common and useful metadata attributes, though it's been criticised on numerous grounds:

    en.wikipedia.org/wiki/Dublin_C

    The US Library of Congress has its own systems, notably the LoC Classification and LoC Subject Headings. Otlet himself came up with the Decimal Classification. (Both LoC and Otlet based their work significantly on that of Melville Dewey, though LoC also inherited Thomas Jefferson's personal book classification structure, as it was Jefferson's collection which initiated the Library of Congress, and if you're interested in that, there are about a century and a half of Librarian's Reports to Congress which detail the history of how that collection (and its physical infrastructure) developed: catalog.hathitrust.org/Record/ with recent editions (past 20 or so years) at the LoC itself: loc.gov/about/reports-and-budg)

    A key point that's often forgotten is that metadata serves users' and archivists' needs, and NOT the interests of authors or publishers. This gives rise to two major issues:

    • Self-classification or description (including full-text -search-based-access as is common online) elevates author and publisher interests over readers. SEO, spam, and clickbait are amongst the highly predictable outcomes of this.

    • Reader and archivist concerns change with time. It's pretty fascinating to look at various Global Classifications Of All Knowledge over time, dating to, say, Aristotle and earlier, but notably Francis and Roger Bacon (no relation), Denis Diderot, Voltaire, etc. Encyclopedia organisational systems especially are a pretty fascinating insight.

    The US LoC is criticised for being US-centric, and anchored in 19th (and 18th) century thinking. Both points are absolutely true, but they're also a reflection of where the collection originated and who it served. In particular, some idosyncracies (the vast sections of History devoted to the US and Americas, relative to the Rest Of the World, say), reflect the actual physical collection and the fact that most of the history books included covered those regions.

    The Librarian's letters beginning around the turn of the 20th century address expansion and revision of the classification system. I've spent a lot of time going through it, and find a few interesting bits such as, say, the legal classification of state law, which is utterly dominated by two states in particular: New York and California. (Several other mostly north-eastern / industrial states are also relatively large.) Again: that's where the interesting detail happens to lie.

    And yes, religion, culture, social groups and movements, etc., are all subject to various forms of abuse, neglect, and/or revision over time. To that extent I find the LoC's classifications in that the have evolved mechanisms to adapt to change over time particularly commendable. Not perfection, but moving toward it, most of the time.

    #Libraries #Librarians #LibraryOfCongress #Cataloging #Catalogs #ClassificationSystems #DocumentManagement #Metadata

  7. Whitespace in filenames is a major category error IMO.

    OTOH, filenames themselves (and filesystems as presently incarnated) are also grossly insufficient for many needs. It's interesting to note, for example, that on Android (and possibly iOS), databases (usually sqlite) have emerged as the de-facto default persistent data storage mechanism, even for content which would normally be held on a filesystem.

    I've long been looking at questions such as what a document-oriented filesysem (#docFS) or the World Wide Web as fileystem accessible (#webFS) might look like.

    For documents, I've generally arrived at a naming standard which uses underbars (_) to separate elements, hyphens (-) for standard whitespace, and double dashes (--) to indicate punctuated / multiple element (e.g., multiple authors, or a subtitle following a colon or dash). Permitted characters are otherwise 7-bit ASCII alphanumeric ([A-Za-z0-9], with dot as a file extension only, and possibly parentheses.

    So:

    Author-One--Author-Two_Title--Subtitle_YYYY.filetype

    That might have a publisher or journal title added (additional underbar-delimited element after the title(s). Additional contributors (e.g., editors, translator) might be mentioned. And it's possible some identifier (ISBN, OCLC, DOI, LoC call number) might be added, though those are supplemental.

    The idea isn't to fully and completely or precisely represent all aspects of a document or work, but to usefully do so. So yes, that means that foreign charactersets aren't presented, that full author lists aren't included (for scientific paper these can number in the tens to hundreds), etc. But enough to find the work reasonably within a corpus through a directory listing.

    Yeah, I'm familiar with Calibre, Zotero etc., and should really get more familiar with them. But they're clunky enough and not sufficiently universally available (e.g., on Android, where most of my documents live these days, via an e-book reader) that I'm not optimistic they're really a solution.

    (Hoisted from a limited share.)

    #DocumentManagement #Whitespace #OnTheNamingOfCats #OnTheNamingOfFiles #Whatever #SameThing #RockyHorror #MacavitysNotHere #Bombalurina #Effanineffable #OldPossum #TSEliot #DOS #PaulOtlet #Mundaneum

  8. Automatische Klassifikation von Dokumenten mit ChatGPT – sind LLMs geeignet, interne Dokumente wie Rechnungen und Verträge mit öffentlichen AI-Systemen wie ChatGPT zu verarbeiten ? PROJECT CONSULT Blog
    bit.ly/43thlX4

    #AI #KI #ML #GPT #ChatGPT #AutoClassification #Classifcation #Documents #Metadata #Scanning #Rechnung #Vertrag #Indizioerung #Erkennen #Verarbeiten #ArtificialIntelligence #InformationManagement #DMS #DocumentManagement #Capture #IDP #IntelligentDocumentProcessing #PCHH

  9. Automatische Klassifikation von Dokumenten mit ChatGPT – sind LLMs geeignet, interne Dokumente wie Rechnungen und Verträge mit öffentlichen AI-Systemen wie ChatGPT zu verarbeiten ? PROJECT CONSULT Blog
    bit.ly/43thlX4

    #AI #KI #ML #GPT #ChatGPT #AutoClassification #Classifcation #Documents #Metadata #Scanning #Rechnung #Vertrag #Indizioerung #Erkennen #Verarbeiten #ArtificialIntelligence #InformationManagement #DMS #DocumentManagement #Capture #IDP #IntelligentDocumentProcessing #PCHH

  10. Automatische Klassifikation von Dokumenten mit ChatGPT – sind LLMs geeignet, interne Dokumente wie Rechnungen und Verträge mit öffentlichen AI-Systemen wie ChatGPT zu verarbeiten ? PROJECT CONSULT Blog
    bit.ly/43thlX4

    #AI #KI #ML #GPT #ChatGPT #AutoClassification #Classifcation #Documents #Metadata #Scanning #Rechnung #Vertrag #Indizioerung #Erkennen #Verarbeiten #ArtificialIntelligence #InformationManagement #DMS #DocumentManagement #Capture #IDP #IntelligentDocumentProcessing #PCHH

  11. Automatische Klassifikation von Dokumenten mit ChatGPT – sind LLMs geeignet, interne Dokumente wie Rechnungen und Verträge mit öffentlichen AI-Systemen wie ChatGPT zu verarbeiten ? PROJECT CONSULT Blog
    bit.ly/43thlX4

    #AI #KI #ML #GPT #ChatGPT #AutoClassification #Classifcation #Documents #Metadata #Scanning #Rechnung #Vertrag #Indizioerung #Erkennen #Verarbeiten #ArtificialIntelligence #InformationManagement #DMS #DocumentManagement #Capture #IDP #IntelligentDocumentProcessing #PCHH

  12. This year Sharepoint has its 20th anniversary. In all these years Microsoft tried as well to own the Enterprise Content Management market by creating their own definition of ECM. An article in German: bit.ly/3y19Nwi

    #Sharepoint #ECM #EnterpriseContentManagement #Microsoft #ECMS #M365 #DocumentManagement

  13. This year Sharepoint has its 20th anniversary. In all these years Microsoft tried as well to own the Enterprise Content Management market by creating their own definition of ECM. An article in German: bit.ly/3y19Nwi

    #Sharepoint #ECM #EnterpriseContentManagement #Microsoft #ECMS #M365 #DocumentManagement

  14. Happy Easter ☀️ We asked the Easter Bunny to help a bit with a #promotion and, to our own surprise, he agreed. Somewhere on our website there's a coupon code hidden that gives you 25% #discount on our #Mac #apps. Enjoy the egg hunt 🐣 #easter #pkm #documentmanagement #informationmanagement #knowledgemanagement #research #pressrelease devontechnologies.com?utm_cont

  15. 'IDP Intelligent Document Processing Report 2023' – im PROJECT CONSULT Blog haben wir kurz über die neue Studie von Deep Analysis berichtet. In 2023 wird es einen Run auf AI-Unternehmen geben.

    bit.ly/3I7xFUI

    #IDP #ECM #KI #AI #ML #Document #DocumentManagement #DocumentProcessing #IntelligentDocumentProcessing #DeepAnalysis #DMS #Capture #Classification #AutoClassification #Cloud #OnPremise #report

  16. 'IDP Intelligent Document Processing Report 2023' – im PROJECT CONSULT Blog haben wir kurz über die neue Studie von Deep Analysis berichtet. In 2023 wird es einen Run auf AI-Unternehmen geben.

    bit.ly/3I7xFUI

    #IDP #ECM #KI #AI #ML #Document #DocumentManagement #DocumentProcessing #IntelligentDocumentProcessing #DeepAnalysis #DMS #Capture #Classification #AutoClassification #Cloud #OnPremise #report