You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
number one problem for databases is having its contents inaccessible.
in the case of community.quantumland.art/database most of its contents is public information.
whenever possible a link to the source should be added to the pages.
in the case of writings, software, and works, only metadata should be listed, and the responsibility of keeping the content alive is:
of the publishers, who might put it in open access or not,
of the developers who might ensure the software can run,
of the creators who own the copyright rights,
in the case of people entries, all content on this page is of the responsibility of the person itself who can contribute to this repo to add their own bio and links to personal website, etc.
and in the case of events a link to the original event page should be at the top of the page. However, since events are much likely to be temporary, and much more prone to having its page disappear, it is strongly advisable to also add an archive link to that original event on wayback machine
now, i wonder if there is a way to automate the process of creating waybackmachine archives in ruby.... but that will be another issue, for right now, we just need to make sure these ideas are clear in the FAQs.
The text was updated successfully, but these errors were encountered:
I can see this being a ruby plugin that checks for frontmatter keys named URL and archived-URL and if the first exist but not the second one, then fetches an archived link for the URL and adds that to the frontmatter.
Conversely, we will need a way to display both on the pages.
number one problem for databases is having its contents inaccessible.
in the case of community.quantumland.art/database most of its contents is public information.
whenever possible a link to the source should be added to the pages.
in the case of
writings
,software
, andworks
, only metadata should be listed, and the responsibility of keeping the content alive is:in the case of
people
entries, all content on this page is of the responsibility of the person itself who can contribute to this repo to add their own bio and links to personal website, etc.and in the case of
events
a link to the original event page should be at the top of the page. However, since events are much likely to be temporary, and much more prone to having its page disappear, it is strongly advisable to also add an archive link to that original event on wayback machinenow, i wonder if there is a way to automate the process of creating waybackmachine archives in ruby.... but that will be another issue, for right now, we just need to make sure these ideas are clear in the FAQs.
The text was updated successfully, but these errors were encountered: