JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CETIS-METADATA Archives


CETIS-METADATA Archives

CETIS-METADATA Archives


CETIS-METADATA@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CETIS-METADATA Home

CETIS-METADATA Home

CETIS-METADATA  October 2003

CETIS-METADATA October 2003

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Secondary Metadata Part1

From:

John Casey {DAICE} <[log in to unmask]>

Reply-To:

John Casey {DAICE} <[log in to unmask]>

Date:

Fri, 10 Oct 2003 16:20:00 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (242 lines)

Hi Phil and Aida

Your comments have been a great help:

Phil (his comments are below)
I like your idea though for representing this information. One of the things
that is emerging in our project is that this kind of information can be far
more valuable than the object it may be associated with. Your suggestion
would make it easier I think to update this information.

Aida (seperate post)
Aida Slavic has just posted me suggesting that what I am talking about is a
secondary resource rather than secondary metadata and that makes a lot of
sense to me (Thanks Aida) which  is what Phil is saying as well. Aida also
gives this hierarchy of information about a resource which related to the
'distance' it is from the original - I hope I am not misrepresenting you
here Aida:

primary (learning resources)
secondary (information about learning resources)
tertiary (directory/compendium of information on learning resources)

Me
So, I think I have a solution (which is not bad for a Friday afternoon)

1. stop calling this stuff secondary metadata and call it secondary
resources
2. when the object is made associate any  secondary resources with it
suggested and identify it in the LOM as Phil suggests.

From an educational point of view this is also quite a handy way of
separating pedagogic information from the resource itself and making it
possible to access and share that separately. One of part of our project is
concerned with using a simple pedagogic framework (there are many) based on
the work of Tom Shuell that will give our project a basic common pedagogic
vocabulary.

We will probably still put the first version of this secondary information
in the object to start with as well, but after that we will update the
separate secondary resource and see how we go.

So one last question: what is secondary metadata? :-)

Thanks a lot

John

> John Casey
> Project Officer
> Learning to Learn  - an X4L Project
> DAICE
> Airthrey Castle
> University of Stirling
> Stirling
> FK9 4LA
> Tel: +44 (0)1786 467943
> email: [log in to unmask]
        web: http://www.stir.ac.uk/departments/daice/l2l/


-----Original Message-----
From: Phil Barker [mailto:[log in to unmask]]
Sent: 10 October 2003 14:03
To: John Casey {DAICE}
Cc: [log in to unmask]
Subject: Re: Secondary Metadata Part1


Hi John,
My solution to this is similar, but I don't think of it as secondary
metadata. Metadata has to be *structured* data about data. I think what you
are talking about, and what is needed, is further information. So, I would
create the tutor notes/suggestions/design ideas/reviews etc in a suitable
format (html, pdf, rtf, word [in rough order of preference]). In an ideal
world I would give it an ID (POI, DOI ...) and put it on a webserver / in a
repository so that it gets a URL. Then in the LOM record for the original
resource I would put

relation
  -kind = isReferencedBy
  -Resource
     -Identifier
        - Catalog = [POI, DOI, ...]
        - value = [id]
     -Identifier
        - Catalog = URL
        - value = http://...
     -Description = "a [case study] of the use of this resource ..."


Alternatively or addtionally in the metadata for the additional information
resource I would use the LOM or DC relation field with relationship kind of
references to point back to the original resource preferably using its ID,
so that a service could come to my metadata catalogue of additional
resources and say "give me additional information about the resource known
as [id]". (There's a use case for identifiers there for anyone interested)


Phil.


John Casey {DAICE} wrote:

> Apologies for cross postings
>
> Dear All
> The question of secondary metadata (tutor notes, suggestions, design
ideas,
> reviews etc) has been a vexed one and has thrown up some interesting
debate,
> including the question of whether anyone wants it or not. That debate, for
> me, leads to some very interesting places but I don't what to explore them
> just yet....Instead I want ask a simple question and get your opinions.
>
> Secondary Metadata: The project I am working on and the teachers I am
> working with want to use secondary metadata in the context of learning
> objects as an extension of their current practice (in fact they already
use
> it in their normal 'real world' non-digital work). But we have some
> problems. The annotations field is not much good for it and a restricted
or
> shared vocabulary looks unlikely (or even desirable given the multiplicity
> of pedagogic models out there - from the ever-present transmission model
to
> some of the more 'far-out' models, if you are interested in the models
this
> link is very handy http://tip.psychology.org/).
>
> So, instead of trying to bend the LOM (Learning Object Metadata) into to
> doing something it was not really designed to do what about this simple,
and
> crude, suggestion?
>
> For those that want secondary metadata then they create it in a rich text
> file and place it in an agreed  place within the object. If that is a
> workable way forward then it would be good if the file had a common name
> like say 'notes'. This way all we would be specifying would be where the
> secondary metadata is located in an object and where people should look if
> they wanted to find it. Of course many objects would not have any
secondary
> metadata - i.e. it would not be mandatory. But if there was any then it
> would be useful if there was a convention to place it somewhere and give
it
> a common name.
>
> What goes inside the secondary metadata file would be totally up to the
> authors / creators etc and if you were interested in what they had to say
> you would have to engage with that on their terms, at least initially, -
> rather like we do in the real world.
>
> So, this secondary metadata file would be just a 'common space' where
> secondary metadata could be placed and read - by people, not machines. If
> this was so then we could say in the annotations field of the LOM "see the
> 'notes' file for more information' - some such. If we agreed on a set name
> for the secondary metadata file the presence of that secondary metadata
> information (yes /no) could even be denoted in some way in the LOM - and
be
> machine readable.
>
> They way I see it metadata and learning objects exist on a spectrum which
at
> the 'sophisticated' end have detailed 'well formed' metadata and may have
> SCORM and Learning Design attributes and characteristics - and very
exciting
> and full of potential all that is.
>
> [But the development of these technologies and things like the
integration
> of runtime systems, learning objects, student records and enterprise
systems
> and so on is also throwing up (as they do) lots of unforeseen questions
> about the our professional cultures and institutions. See this article for
> interesting ESRC research on this relatively neglected 'systems' aspect of
> our kind of work: http://www.ariadne.ac.uk/issue24/virtual-universities/]
I
> digress....
>
>
> As we go back down through the spectrum of learning objects we move
towards
> the 'primitive' end where people are using repositories as very simple
> digital libraries - and getting very immediate benefits, that's where I am
> coming from.
>
> What do you think?
>
> Thanks
> John
>
>
>
>
>
>
>
>>John Casey
>>Project Officer
>>Learning to Learn  - an X4L Project
>>DAICE
>>Airthrey Castle
>>University of Stirling
>>Stirling
>>FK9 4LA
>>Tel: +44 (0)1786 467943
>>email: [log in to unmask]
>
>         web: http://www.stir.ac.uk/departments/daice/l2l/
>
>
> --
> The University of Stirling is a university established in Scotland by
> charter at Stirling, FK9 4LA.  Privileged/Confidential Information may
> be contained in this message.  If you are not the addressee indicated
> in this message (or responsible for delivery of the message to such
> person), you may not disclose, copy or deliver this message to anyone
> and any action taken or omitted to be taken in reliance on it, is
> prohibited and may be unlawful.  In such case, you should destroy this
> message and kindly notify the sender by reply email.  Please advise
> immediately if you or your employer do not consent to Internet email
> for messages of this kind.


--
Phil Barker                            Learning Technology Adviser
      ICBL, School of Mathematical and Computer Sciences
      Mountbatten Building, Heriot-Watt University,
      Edinburgh, EH14 4AS
      Tel: 0131 451 3278    Fax: 0131 451 3327
      Web: http://www.icbl.hw.ac.uk/~philb/

--
The University of Stirling is a university established in Scotland by
charter at Stirling, FK9 4LA.  Privileged/Confidential Information may
be contained in this message.  If you are not the addressee indicated
in this message (or responsible for delivery of the message to such
person), you may not disclose, copy or deliver this message to anyone
and any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.  In such case, you should destroy this
message and kindly notify the sender by reply email.  Please advise
immediately if you or your employer do not consent to Internet email
for messages of this kind.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
October 2022
August 2022
July 2022
May 2022
April 2022
March 2022
January 2022
November 2021
September 2021
May 2021
April 2021
February 2021
November 2020
September 2020
August 2020
July 2020
June 2020
March 2020
February 2020
September 2019
August 2019
July 2019
June 2019
April 2019
February 2019
December 2018
November 2018
September 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager