dump friendly repository management question

I am contemplating a repository layout which uses the "all projects in
one repository" pattern. I want to be able to dump individual projects,
with all the history, and load them into different repositories in the
future. Given the nature of svndumpfilter{1..3}, I am concerned about
copy/move operations.
 
As time passes, projects become inactive for one reason or another.
These projects would be "archived". One proposal is to move those
projects into a folder called "Archived". However, as soon as this is
done, we will lose the ability to extract those projects, with history,
from the repository. I want to avoid this problem. However, I don't
want visual clutter in the repository. We want to quickly differentiate
between active and archived projects visually.
 
I am also unsure about the consequences of moving a project to Archived,
and later moving it back to its original location.
 
Do any of you have experience in this area you can share with me? What
works best for you?
 
I have one idea at the moment: create an "archived" user and once a
project is archived, make it readable only by user "archived" and group
"Admin".
 
 

--
David Bicking
Heritage Holdings IT
55 Farmington Ave., Suite 605
 
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************