Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Biology
BiologyBotanyMicrobiologyEntomologyEvolutionPaleontology
Chemistry
General ChemistryAnalytical ChemistryElectrochemistryOrganic Synthesis
Earth Science
GeologyMineralogyOceanographyMeteorologyEarthquakes
Physics
General PhysicsResearchRelativityParticle PhysicsElectromagnetismFusionOpticsAcousticsNew Theories

Natural Science Forum / Biology / Paleontology / January 2005



Tip: Looking for answers? Try searching our database.

Request for help with thesis

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
tuvas@ifi.uio.no - 21 Jan 2005 23:09 GMT
Hi

I am a master student at the faculty of computer science, University of
Oslo. My master thesis deals with collection software. One milestone is
to determine user requirements for collection software, at the moment
restricted to fossil collections. More precisely, I need input from
potential users of such software on needs and demands they want such
software to meet.

And for this I need help from the collectors on this forum. The views
of serious collectors, like you, would be important input when
designing this software.

This is what I want to know:
In a utopian software for collection management what information about
the spesific fossil would you like to register? For example a
description of the object or its condition may be something you may
like to register in a database. What other properties would you like to
see in a computer program for managing your collection fossils.

Thank you in advance, any input is much appreciated.
Tuva Solstad
tuvas (at) ifi.uio.no
Edward  Hennessey - 22 Jan 2005 04:03 GMT
> Hi
>
[quoted text clipped - 19 lines]
> Tuva Solstad
> tuvas (at) ifi.uio.no

T.S.:

In your place, I would search under +museum +(listserve OR listserver) and
then try +paleontology +(listserve OR listserver), selecting the appropriate
results and then posting to those lists. Paleonet is one fine list which you
should direct your attention to.

Regards,

Edward Hennessey

nohalozzyzxnohalo@noyahoo.com - no,no,no.
rcook5@TAKEOUTmindspring.com - 22 Jan 2005 04:08 GMT
>Hi
>
[quoted text clipped - 19 lines]
>Tuva Solstad
>tuvas (at) ifi.uio.no

Measurements, measurements, measurements!

multi-dimensional visualizations of the measurements would be nice.

--RC

"Sometimes history doesn't repeat itself. It just yells
'can't you remember anything I've told you?' and lets
fly with a club.
          -- John W. Cambell Jr.
Joe Rat - 22 Jan 2005 09:35 GMT
> Hi
>
[quoted text clipped - 19 lines]
> Tuva Solstad
> tuvas (at) ifi.uio.no

It should hold the map or utm coordinates where it was found
Stratigraphical information
Description
Where you are holding it in your collection (room, cupboard,
drawer)
Graphics (photo(s) of object or finding place
Name after determination
collector
determinator
sample#

Clearly if all this info would be stored
every record would be large especially
if graphics are contemplated.
Therefore it would be well to
use a DB with linked tables through
an index of the Main table so that
you can have, without wasting space
fossils with 0 images or 10 images.
In the same way you could have
some with and without description.

Security is an issue as well.
You need log-ins with passwords
for users who can only consult
and users that can modify.
When more people can modify
you need record locking
Roll-back of a changing session is
always a good thing.

VB with SQL is what I use
myself

Regs

Joe Rat  8:o)
Don Kenney - 24 Jan 2005 12:13 GMT
First of all, you should know that very few serious paleontologists
are active in this newsgroup there days, so you may want to ask
elsewhere as well.

Two places where it would make sense to ask would be museums and
institutes of higher learning -- specifically the geology and/or
paleontology departments.

As for what should go into a data base

1.  Species and genus of specimen (not always known, so while it's a
useful index, it can't be the only one.  And it isn't unique of course
because a collection may contain a number of specimens of the same
critter ... or multiple different critters on the same slab)).  Oh
yes, and maybe Common name as well -- eg. Isurus is the "mako shark".
And some genera and species have two names e.g. Isurus is also called
Oxyrhinus in some older references and collections.

2.  Locality collected.  Coutry; state/province/etc, County, City, one
or two more levels below that.  Ideally there would probably be a
separate data base with coordiantes (maybe multiple as various systems
are used -- UTM, lat-long,range-azimuth from a reference point,
"legal" (range, Section, Township), Directions to the site.  Comments
(e.g. "Narrow outcrop of rotten rock 50 feet up rattlesnake infested
cliff")

3.  Geologic Age(e.g Cambrian), Paleontolgic (e.g. Albertan)
-Formation collected from.  Note that there may be further
subdivisions of fromations -- members and beds/layers within members.
and possibly superdivisions such as Group or Series

4.  Some sort of Reference number

5.  Some sort of  memo field(s) for comments and notes -- possibly
multiple and tied somehow to other fields such as locality and age.

There's surely much more, but I have to get to work  Good Luck

>Hi
>
[quoted text clipped - 19 lines]
>Tuva Solstad
>tuvas (at) ifi.uio.no
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.