Masters

[Christopher Gutteridge]

(these are just some notes as I'm working hard with BIBO today and want
to note anything interesting I run into)

My system only knows a thesis is "masters", with no distinction between
science & arts. I would like to make a very minor suggestion to make a
super class of ms and ma which reflected generic "masters", but it's not
a very big deal.

--
Christopher Gutteridge -- http://www.ecs.soton.ac.uk/people/cjg

Lead Developer, EPrints Project, http://eprints.org/

Web Projects Manager, School of Electronics and Computer Science,
University of Southampton.

[Frederick Giasson]

Hi Christopher!

> (these are just some notes as I'm working hard with BIBO today and
> want to note anything interesting I run into)
>
> My system only knows a thesis is "masters", with no distinction
> between science & arts. I would like to make a very minor suggestion
> to make a super class of ms and ma which reflected generic "masters",
> but it's not a very big deal.

Did you take a look at this example:

http://bibliontology.com/examples#Thesis

(I like having this new web site up and running :) )

Just to make sure we are on the same page: "ThesisDegree" is not a type
of document. It is a "status" that a "Thesis" document can have. This
means that we could create a new instance of the class ThesisDegree that
would be a un-named Master degree. So, there won't be any hierarchy of
master degrees, but really just another instance of the ThesisDegree class.

Not sure if I am clear? Does that make sense?

Thanks!

Fred

[Bruce D'Arcus]

On Thu, Feb 11, 2010 at 2:05 PM, Frederick Giasson <fr...@fgiasson.com> wrote:
> Hi Christopher!
>>
>> (these are just some notes as I'm working hard with BIBO today and want to
>> note anything interesting I run into)
>>
>> My system only knows a thesis is "masters", with no distinction between
>> science & arts. I would like to make a very minor suggestion to make a super
>> class of ms and ma which reflected generic "masters", but it's not a very
>> big deal.
>
> Did you take a look at this example:
>
> http://bibliontology.com/examples#Thesis
>
> (I like having this new web site up and running :) )
>
> Just to make sure we are on the same page: "ThesisDegree" is not a type of
> document. It is a "status" that a "Thesis" document can have.

Well, just to avoid confusion, it's a bibo:degree.

Bruce

[Frederick Giasson]

Hi!

> Well, just to avoid confusion, it's a bibo:degree.
>

<some-resource> a bibo:Thesis;
bibo:degree bibo_degrees:mx.

To remove all possible confusion. Remember that bibo:degree's domain is
a bibo:Thesis.

Thanks,

Fred

[Bruce D'Arcus]

Right; just wanted to distinguish it from our bibo:status property.

Bruce

[Christopher Gutteridge]

Thanks guys. So I've got a

foo a bibo:Thesis

And all I know is that it's a "masters" but not which kind. I guess I could mint my on URI?

foo bibo:degree <http://eprints.org/mystuff/degrees/masters>

Or just leave it as it's not that useful...

We also have "EngD" as a thesis type....

[Bruce D'Arcus]

On Thu, Feb 11, 2010 at 3:12 PM, Christopher Gutteridge
<c...@ecs.soton.ac.uk> wrote:
> Thanks guys. So I've got a
>
> foo a bibo:Thesis
>
> And all I know is that it's a "masters" but not which kind. I guess I could
> mint my on URI?
>
> foo bibo:degree <http://eprints.org/mystuff/degrees/masters>

Hmm .. how common is this case? What's your source data?

In any case, we need ot figure out a policy here.

> Or just leave it as it's not that useful...
>
> We also have "EngD" as a thesis type....
>
>
> Bruce D'Arcus wrote:
>
> On Thu, Feb 11, 2010 at 2:14 PM, Frederick Giasson <fr...@fgiasson.com>
> wrote:
>
>
> Hi!
>
>
>
> Well, just to avoid confusion, it's a bibo:degree.
>
>
>
> <some-resource> a bibo:Thesis;
> bibo:degree bibo_degrees:mx.
>
> To remove all possible confusion. Remember that bibo:degree's domain is a
> bibo:Thesis.
>
>
> Right; just wanted to distinguish it from our bibo:status property.
>
> Bruce
>
>
>
> --
> Christopher Gutteridge -- http://www.ecs.soton.ac.uk/people/cjg
>
> Lead Developer, EPrints Project, http://eprints.org/
>
> Web Projects Manager, School of Electronics and Computer Science,
> University of Southampton.
>

> --
> You received this message because you are subscribed to the Google Groups
> "Bibliographic Ontology Specification Group" group.
> To post to this group, send email to
> bibliographic-ontolog...@googlegroups.com.
> To unsubscribe from this group, send email to
> bibliographic-ontology-spec...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/bibliographic-ontology-specification-group?hl=en.
>

[Stuart A. Yeates]

On Fri, Feb 12, 2010 at 9:30 AM, Bruce D'Arcus <bda...@gmail.com> wrote:
> On Thu, Feb 11, 2010 at 3:12 PM, Christopher Gutteridge
> <c...@ecs.soton.ac.uk> wrote:
>> Thanks guys. So I've got a
>>
>> foo a bibo:Thesis
>>
>> And all I know is that it's a "masters" but not which kind. I guess I could
>> mint my on URI?
>>
>> foo bibo:degree <http://eprints.org/mystuff/degrees/masters>
>
> Hmm .. how common is this case? What's your source data?

In an institutional setting, this is a very common distinction. We run
the opposition's institutional repository (dspace to Chris's eprints),
but most of our documents are organised by 'grade' of thesis. See
http://researcharchive.vuw.ac.nz/handle/10063/7

The difference between doctoral, masters theses and other course work
(bachelors with honors reports, reports from a number of our nursing
qualifications, etc.) is the cornerstone of both our collections
policy and the story we tell the rest of our institution about the
role of the repository.

cheers
stuart

[Frederick Giasson]

Hi!

> foo a bibo:Thesis
>
> And all I know is that it's a "masters" but not which kind. I guess I
> could mint my on URI?
>
> foo bibo:degree <http://eprints.org/mystuff/degrees/masters>
>
> Or just leave it as it's not that useful...
>
> We also have "EngD" as a thesis type....

You can create one. Just make sure that it is of type bibo:ThesisDegree.

However, it could make sense to add it in BIBO too.

I create a new page on the website to list all propositions for the next
version. I added this one. Take a look here:

http://bibliontology.com/changelog/next-changes

Also notice the changes in the menu items.

Thanks,

Fred

[Patrick Murray-John]

> I create a new page on the website to list all propositions for the next
> version. I added this one. Take a look here:
>
> http://bibliontology.com/changelog/next-changes
>
> Also notice the changes in the menu items.
>
>
> Thanks,
>
>
> Fred
>
>

Fred,

I might just be getting ahead of the plans for the site, but it might
make long-term sense to use the CCK and Views modules to make a
"Proposed Change" content type and pull them all together into a page
with views. Don't know if that'd be making the site too complex for
something that just launched, but long-term it could be a way to make
maintenance easier down the road by making each proposals easier to track.

Love the site!

Patrick

[Frederick Giasson]

Hi Patrick!

> I might just be getting ahead of the plans for the site, but it might
> make long-term sense to use the CCK and Views modules to make a
> "Proposed Change" content type and pull them all together into a page
> with views. Don't know if that'd be making the site too complex for
> something that just launched, but long-term it could be a way to make
> maintenance easier down the road by making each proposals easier to
> track.

Certainly not too complex! It is exactly what I did for the OpenStruct
community website with the changelog (content type + views) on:
http://community.openstructs.org, like:
http://community.openstructs.org/source-code/change-logs/structwsf/

Just a lack of time on my side, for now. However, if you are willing to
do this, I can enable views and such. Otherwise I will try to do it
tomorrow or sometime next week.

What would you like to do?

Thanks,

Fred

[Patrick Murray-John]

Fred,

I'd be happy to go in and do what I can.

Patrick