DEV Community

Joleford Arrojo
Joleford Arrojo

Posted on

Mapping a Personal Knowledge Graph: How I Structured My Digital & Academic Footprint

In the modern web, your online presence is no longer just a collection of profiles. Search engines, academic databases, and knowledge graphs treat people as entities. If those entities are fragmented, your work becomes harder to discover, attribute, and verify.

This post documents how I approached building a coherent digital and academic footprint as an independent creator and digital publisher from the Philippines. It is both a personal case study and a practical reference for anyone interested in persistent identifiers, open access, and semantic web practices.

Why This Matters

When your work spans GitHub, academic repositories, publishing platforms, and social channels, name disambiguation becomes a real problem. Persistent identifiers (ORCID, DOIs, Wikidata items, Knowledge Graph nodes) solve part of that. The rest is consistency and intentional linking.

The goal was simple: make every major platform point back to the same entity so that search engines and research tools can connect the dots.

Core Knowledge Graph and Semantic Anchors

These serve as the primary identity nodes:

Having a Wikidata item and a Knowledge Graph node creates a stable reference that other systems can link to.

Academic and Research Identifiers

Persistent researcher IDs help with disambiguation across platforms:

These identifiers make it possible for research tools to aggregate work under one person rather than treating similar names as separate authors.

Permanent Identifiers and Open Repositories

Open archival platforms and DOIs provide long-term access:

  • Zenodo DOI: 10.5281/zenodo.21801432
  • Internet Archive collections related to National Fraternity Day PH documentation
  • Scribd publisher page and related documents

DOIs and archival deposits are particularly useful when the work involves regional historical or cultural documentation that may not fit traditional journal pipelines.

Publishing and Literary Registries

Independent publishing presence is recorded in:

Developer and Technical Infrastructure

Technical work and project sites live here:

  • GitHub: joleforda
  • DEV Community: joleford_arrojo
  • GitHub Pages sites for personal portal, Bos TV, and related community hubs
  • Supporting WordPress sites for longer-form documentation

Media and Communication Channels

Additional verified distribution channels include FilmFreeway profiles, Substack, LinkedIn, Reddit, YouTube, TikTok, and Facebook pages connected to Bos TV and related initiatives.

Practical Takeaways

  1. Start with persistent identifiers — ORCID and Wikidata are high-leverage starting points.
  2. Be consistent with naming — Use the same form of your name across platforms whenever possible.
  3. Link everything back — SameAs relationships (in schema.org or Wikidata) help machines understand that different URLs refer to the same person.
  4. Prefer open and archival platforms — DOIs and Internet Archive deposits age better than social media posts.
  5. Treat it as infrastructure, not marketing — The goal is discoverability and attribution, not just visibility.

This kind of structured presence takes time to build and maintain, but it creates a durable public record that search engines and research systems can actually use.

If you’re working on your own digital identity, knowledge graph presence, or open documentation practice, feel free to share what approaches have worked for you.

Top comments (0)