Suggestion: The "link URL" functionality should be useable to keep track of whether (or not) multiple URLs have been collected into a single UUID's archive. For example the <UUID>.json file could have Related UUIDs or Related URLs fields...
Why: Government agencies sometimes organize content in many-branched websites (e.g. this). There may be data resources and download links interspersed throughout multiple interrelated pages, while the top-level page may not contain any archiveable data itself. On the other hand, archiving many sub-pages individually can be confusing. With each URL having its own UUID this can get lead to inconsistent archiving strategies.
Suggestion: The "link URL" functionality should be useable to keep track of whether (or not) multiple URLs have been collected into a single UUID's archive. For example the
<UUID>.jsonfile could haveRelated UUIDsorRelated URLsfields...Why: Government agencies sometimes organize content in many-branched websites (e.g. this). There may be data resources and download links interspersed throughout multiple interrelated pages, while the top-level page may not contain any archiveable data itself. On the other hand, archiving many sub-pages individually can be confusing. With each URL having its own UUID this can get lead to inconsistent archiving strategies.