Hi all,
For my uses, finding the appropriate string (URI) to place into the
subject was difficult. As we're building a CMS that can be installed
(and moved) from server to server (particularly dev to production
server), locking the subjects into a specific URI
(
http://SERVER-1/resource) became problematic -- if moved to the
production server, for example, did we need to run a query renaming
all of the URIs to reflect to the new domain?
Our workaround (or solution) was to use URN instead. Rather than
store a URL (http://...) we construct a URN
(urn:our_project:version:1234). This requires the addition of another
table in our database (we have a few additions, but for the sake of
argument...), which houses the versions for each page. The row ID is
the number that get's placed into the URN, and we have a field for
"slug" which reflects the URL of the page being called (the URL
segment of the page without mention of the domain name). So, for
example, given a specific page, we grab its row from the versions
table based on the slug field, return the version ID, then grab its
metadata from ARC using the newly constructed URN based on that
version ID.
Hopefully helpful,
Craig