> Is there any way in which we can segregate the Single database into a number
> of databases.
How would you represent the "breaks" in the content as you are
downloading a webpage into separate pages? You can easily manage this
with a combination of the exclusionlist.txt, and creating some stanzas
in your .pluckerrc file, breaking a large site into several smaller
sites. Sitescooper may be able to do this as well, I think.
> This will allow the user to selectively Download and create small databases
> instead of one large database.
I don't see the advantage though, the overall size of 10 smaller
databases which make up one website vs. one larger database of the same
website will always be larger than one single database (assuming the
exact same content). Why would you want to do this?
> This can be done via the Plucker document library page
> but in that case teh links which are present in pages will not work
> how can we make links present in one pdb open pages present in other
> databases
An interesting idea: launching another separate DB from within an
existing DB. This would actually be a smart way to use the
plucker:/dbname syntax in a URI fragment, instead of the local files it
represents now (when did that slip in under the radar?)
Mike, how hard would it be to launch another db from within an existing
db, assuming the parser could create the right ID for it using a URI
like <a href="plucker:/wired.pdb">Wired</a> or something like that?
/d
