Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

if logged in, copy URI link includes my namespace resulting in 404

Open
#148 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
frontend

Research direction

Start by reproducing the copied URI behavior in current interlex/NewInterlex while logged in and logged out, then trace where the term link is constructed. Compare unedited terms with terms added to an ontology but not modified; done when copied links use the published standard IRI and resolve for users outside the namespace.

Written by the indexing model from the issue text.

Description

If I'm using current interlex and want to share a term URI, I get the same link construction wherein NewInterlex automatically puts all terms in my namespace, even if I have made no changes.

This means that my copied links give a 404 to anyone that's not me, (including me if i'm not logged in).

http://uri.interlex.org/dariodippi/ilx_0103471 vs https://interlex.dev.metacell.us/base/ilx_0103471/overview

Expected behavior -

  1. If a term has not been edited, the IRI should be the standard IRI that is available to everyone.
  2. if i haven't added a term to my ontology, the term is unedited, and therefore should be the base/default term IRI.
  3. I must add the term to an ontology before i can make changes to it.

In sum, if a term is added to my ontology, but has no modifications, I believe it should resolve to the "published" term IRI, not locked within my namespace

Dominant language
JavaScript
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaCell/interlex

All issues in MetaCell/interlex

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.