Reply to thread

Message

<blockquote data-quote="Morrus" data-source="post: 6210173" data-attributes="member: 1">Kinda.&nbsp; Each is its own distinct entity.&nbsp; So I might browse Janx's Pathfinder Feats Library or you might browse Morrus' FASA Star Trek Starships.&nbsp; There might be duplication in that some users might choose to do similar things - but that's OK.&nbsp; Choice is good; the better ones will get used more.Terminology I'm using here: A database contains records, each of which has a number of fields.&nbsp; I don't know if that's the same terminology you use, but it was the terminology used at the NHS database I used when I worked part time at a hospital 25 years ago, and the library database I used at my local library, and the terminology used by the database program I painstakingly typed out 2E kits and Star Trek spaceships in many years ago!&nbsp; So Janx's 2E Monster Database contains monsters (records) each of which has a number of fields (hit dice, size, other stats).So you're right in that they'll be in categories.&nbsp; The categories could be anything; I'll just set up categories as and when they're needed.&nbsp; So the AD&amp;D 2E category might contain a number of folks' databases - your monster one, perhaps, and a spells one I made.Once you're looking at a specific database, you can search it (obvious) or use filters via little dropdowns which say &quot;X is Y than Z&quot; - so &quot;Hit Dice is smaller than 6&quot; or &quot;Challenge Rating is larger than 12&quot; or &quot;Name contains the word goblin&quot;.&nbsp; These are basically =, &gt;, &lt;, contains, does not contain, and so on.&nbsp; A fairly standard set of common operators.&nbsp; Right now I'm thinking three filters will be available - so you can filter a database by up to three things.&nbsp; Or just search it, of course.Each database is owned by a person.&nbsp; That person can set permissions for it.&nbsp; Permissions to read, to write, etc.&nbsp; They might even be able to charge for access to it (which would rarely be a good idea - but some smaller companies/IP holders might like to use it for a DDI compendium style thing without having to code their own one).</blockquote>

[QUOTE="Morrus, post: 6210173, member: 1"] Kinda. Each is its own distinct entity. So I might browse Janx's Pathfinder Feats Library or you might browse Morrus' FASA Star Trek Starships. There might be duplication in that some users might choose to do similar things - but that's OK. Choice is good; the better ones will get used more. Terminology I'm using here: A database contains records, each of which has a number of fields. I don't know if that's the same terminology you use, but it was the terminology used at the NHS database I used when I worked part time at a hospital 25 years ago, and the library database I used at my local library, and the terminology used by the database program I painstakingly typed out 2E kits and Star Trek spaceships in many years ago! So Janx's 2E Monster Database contains monsters (records) each of which has a number of fields (hit dice, size, other stats). So you're right in that they'll be in categories. The categories could be anything; I'll just set up categories as and when they're needed. So the AD&D 2E category might contain a number of folks' databases - your monster one, perhaps, and a spells one I made. Once you're looking at a specific database, you can search it (obvious) or use filters via little dropdowns which say "X is Y than Z" - so "Hit Dice is smaller than 6" or "Challenge Rating is larger than 12" or "Name contains the word goblin". These are basically =, >, <, contains, does not contain, and so on. A fairly standard set of common operators. Right now I'm thinking three filters will be available - so you can filter a database by up to three things. Or just search it, of course. Each database is owned by a person. That person can set permissions for it. Permissions to read, to write, etc. They might even be able to charge for access to it (which would rarely be a good idea - but some smaller companies/IP holders might like to use it for a DDI compendium style thing without having to code their own one). [/QUOTE]

Verification