Re: [Ossmole-discuss] FLOSSmole DOIs

[Andrea Wiggins <awiggins@sy...>]

Actually, the reason I suggested SourceForge as place of publication  
is because that is where some of the FLOSSmole data is "published" and  
available for download. The other publication location would be Google  
Code; we don't actually host any of the datasets ourselves. I think  
Kevin's point reflects the ambiguity over publisher versus producer  
more than publication place.

A

On Feb 24, 2009, at 11:52 AM, Kevin Crowston <crowston@...>  
wrote:

> It's an interesting point--when is data published? SourceForge is  
> where we got the data but it wasn't a dataset 'til we pulled it  
> together.
>
> So maybe we want to put FLOSSmole down as the place of publication?
>
> SourceForge, etc. need to be there, but I think somewhere else. (I'm  
> contradicting what I said earlier, but after further thought...)
>
> On 23 Feb 2009, at 2:30 PM, Megan Squire wrote:
>
>> Andrea (and moles) This seems reasonable. I think keeping the
>> publication place as sourceforge is ok. This stuff is very confusing
>> to me - since it's not traditional publishing we just have to guess  
>> on
>> a lot of it.
>>
>> Which of the resource identifiers do you think will end up in our  
>> DOAP
>> file, or will we use many/all of them?
>>
>> -megan
>>
>> On Fri, Feb 20, 2009 at 9:02 AM, Andrea Wiggins <awiggins@...>  
>> wrote:
>>> Hello all -
>>> We've gotten the go-ahead to start assigning DOIs[1] to data sets!  
>>> More
>>> precisely, Syracuse University is now an authorized DOI  
>>> publication agent
>>> via TIB [2], the registration agency for scientific primary and  
>>> secondary
>>> data, which is operated by the German national library of science  
>>> and
>>> technology. The reason to do this is that it allows better data  
>>> citations
>>> and serves as a permanent identifier.
>>> The process of assigning DOIs to data sets involves resolving a  
>>> few metadata
>>> ambiguities, so I wanted to check with the FLOSSmole user  
>>> community for any
>>> suggestions before we finalize the details. Please feel free to make
>>> suggestions for the 9 fields [3] that are up for consideration;  
>>> the rest are
>>> either fixed or completely unambiguous.  Below, I've pasted in an  
>>> example
>>> XML file for a FLOSSmole dataset DOI definition [4].
>>> There aren't necessarily any right answers here, so any feedback  
>>> on the
>>> proposed DOI naming convention and metadata values would be very  
>>> helpful.
>>> Thanks for your feedback!
>>> Andrea
>>>
>>> [1] http://www.doi.org
>>> [2] http://www.std-doi.de/front_content.php
>>> [3] Fields that are up for discussion:
>>> 1) <DOI> - everything after the 10.4118/ is up to us. The naming  
>>> convention
>>> I've suggested below uses the repository name as a prefix  
>>> (flossmole)
>>> followed by the filename, separated by a dot. This is by no means  
>>> the best
>>> DOI convention, just what occurred to me as reasonably logical. We  
>>> can also
>>> just assign ascending numeric values, e.g. 10.4118/floss.000001,  
>>> as they do
>>> not have to be human-readable.
>>> 2) <resourceIdentifier> I've included the eprints record and data  
>>> set
>>> download URLs as additional identifiers. They are shown as
>>> "ProprietaryIdentifiers" because URL is not a legal type for the  
>>> field (URN
>>> would be, but these are not URNs, strictly speaking).
>>> 3) <creator> Currently Kevin, Megan and James are credited as  
>>> creators, as
>>> they are the PI's for the FLOSSmole project.
>>> 4) <contributor> The contributor is currently defined as the source
>>> repository from which FLOSSmole spidered the data.
>>> 5) <publisher> The publisher is currently defined as the entity that
>>> published the dataset. If we were to issue DOIs for datasets from
>>> FLOSSmetrics, for example, then the publisher would be FLOSSmetrics.
>>> 6) <creationDate> and <publicationDate> are the same in this case;  
>>> as I
>>> understand it, the FLOSSmole data are created and then promptly  
>>> published,
>>> so there's not much point of differentiation. We can choose to use  
>>> one or
>>> the other, or both.
>>> 7) <description> The description shown here is the short abstract  
>>> on the
>>> eprints record.
>>> 8) <publicationPlace> is currently listed as SourceForge.net but  
>>> could just
>>> as appropriately be listed as Elon, NC.
>>> 9) <discipline> is currently listed as softwareEngineering. The  
>>> field is
>>> intended to identify a scientific discipline in the most  
>>> traditional sense;
>>> this was what we thought made the most sense.
>>> [4] Sample XML record
>>> <?xml version="1.0"?>
>>> <resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";  
>>> xsi:noNamespaceSchemaLocation="std-doi.xsd">
>>> <DOI>10.4118/flossmole.fmProjectAuthors2008-May</DOI>
>>> <resourceIdentifiers>
>>> <resourceIdentifier type="ProprietaryIdentifier">http://flosspapers.org/1585/ 
>>> </resourceIdentifier>
>>> <resourceIdentifier type="ProprietaryIdentifier">http://downloads.sourceforge.net/ossmole/fmProjectAuthors2008-May.txt.bz2 
>>> </resourceIdentifier>
>>> </resourceIdentifiers>
>>> <creator>Megan@...</creator>
>>> <creator>Kevin@...</creator>
>>> <creator>James@...</creator>
>>> <contributor>freshmeat</contributor>
>>> <publisher>FLOSSmole</publisher>
>>> <title>fmProjectAuthors2008-May.txt.bz2</title>
>>> <language>en</language>
>>> <structuralType>Digital</structuralType>
>>> <mode>Abstract</mode>
>>> <resourceType>Dataset</resourceType>
>>> <registrationAgency>10.4118</registrationAgency>
>>> <issueNumber>1</issueNumber>
>>> <creationDate>2002-09-17</creationDate>
>>> <publicationDate>2008-05-06</publicationDate>
>>> <description>Freshmeat project authorship data.</description>
>>> <publicationPlace>SourceForge.net</publicationPlace>
>>> <size>
>>> <value>486672</value>
>>> <unit>Bytes</unit>
>>> </size>
>>> <format>text/plain</format>
>>> <edition>1</edition>
>>> <discipline>softwareEngineering</discipline>
>>> </resource>
>>>
>>> Andrea Wiggins
>>> PhD Student, School of Information Studies
>>> Syracuse University
>>> 337 Hinds Hall
>>> Syracuse, NY 13244
>>> awiggins@...
>>> http://www.andreawiggins.com
>>>
>>> --- 
>>> --- 
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>> Open Source Business Conference (OSBC), March 24-25, 2009, San  
>>> Francisco, CA
>>> -OSBC tackles the biggest issue in open source: Open Sourcing the  
>>> Enterprise
>>> -Strategies to boost innovation and cut costs with open source  
>>> participation
>>> -Receive a $600 discount off the registration fee with the source  
>>> code: SFAD
>>> http://p.sf.net/sfu/XcvMzF8H
>>> _______________________________________________
>>> Ossmole-discuss mailing list
>>> Ossmole-discuss@...
>>> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss
>>>
>>>
>>
>> --- 
>> --- 
>> --- 
>> ---------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San  
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the  
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source  
>> participation
>> -Receive a $600 discount off the registration fee with the source  
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Ossmole-discuss mailing list
>> Ossmole-discuss@...
>> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss
>
>
> Kevin Crowston
> Syracuse University                                    Phone:  +1 (315) 443-1676
> School of Information Studies            Fax:    +1 (866) 265-7407
> 348 Hinds Hall                        Web:    http://crowston.syr.edu/
> Syracuse, NY   13244-4100   USA
>
> *PS: The attachment named "PGP.sig" of type "application/pgp- 
> signature" is an electronic signature that may be used to verify  
> that this email came from me if you have PGP or GPG. Otherwise, you  
> may safely ignore the attachment.
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss

Re: [Ossmole-discuss] FLOSSmole DOIs

[Kevin Crowston <crowston@is...>]

It's an interesting point--when is data published? SourceForge is  
where we got the data but it wasn't a dataset 'til we pulled it  
together.

So maybe we want to put FLOSSmole down as the place of publication?

SourceForge, etc. need to be there, but I think somewhere else. (I'm  
contradicting what I said earlier, but after further thought...)

On 23 Feb 2009, at 2:30 PM, Megan Squire wrote:

> Andrea (and moles) This seems reasonable. I think keeping the
> publication place as sourceforge is ok. This stuff is very confusing
> to me - since it's not traditional publishing we just have to guess on
> a lot of it.
>
> Which of the resource identifiers do you think will end up in our DOAP
> file, or will we use many/all of them?
>
> -megan
>
> On Fri, Feb 20, 2009 at 9:02 AM, Andrea Wiggins <awiggins@...>  
> wrote:
>> Hello all -
>> We've gotten the go-ahead to start assigning DOIs[1] to data sets!  
>> More
>> precisely, Syracuse University is now an authorized DOI publication  
>> agent
>> via TIB [2], the registration agency for scientific primary and  
>> secondary
>> data, which is operated by the German national library of science and
>> technology. The reason to do this is that it allows better data  
>> citations
>> and serves as a permanent identifier.
>> The process of assigning DOIs to data sets involves resolving a few  
>> metadata
>> ambiguities, so I wanted to check with the FLOSSmole user community  
>> for any
>> suggestions before we finalize the details. Please feel free to make
>> suggestions for the 9 fields [3] that are up for consideration; the  
>> rest are
>> either fixed or completely unambiguous.  Below, I've pasted in an  
>> example
>> XML file for a FLOSSmole dataset DOI definition [4].
>> There aren't necessarily any right answers here, so any feedback on  
>> the
>> proposed DOI naming convention and metadata values would be very  
>> helpful.
>> Thanks for your feedback!
>> Andrea
>>
>> [1] http://www.doi.org
>> [2] http://www.std-doi.de/front_content.php
>> [3] Fields that are up for discussion:
>> 1) <DOI> - everything after the 10.4118/ is up to us. The naming  
>> convention
>> I've suggested below uses the repository name as a prefix (flossmole)
>> followed by the filename, separated by a dot. This is by no means  
>> the best
>> DOI convention, just what occurred to me as reasonably logical. We  
>> can also
>> just assign ascending numeric values, e.g. 10.4118/floss.000001, as  
>> they do
>> not have to be human-readable.
>> 2) <resourceIdentifier> I've included the eprints record and data set
>> download URLs as additional identifiers. They are shown as
>> "ProprietaryIdentifiers" because URL is not a legal type for the  
>> field (URN
>> would be, but these are not URNs, strictly speaking).
>> 3) <creator> Currently Kevin, Megan and James are credited as  
>> creators, as
>> they are the PI's for the FLOSSmole project.
>> 4) <contributor> The contributor is currently defined as the source
>> repository from which FLOSSmole spidered the data.
>> 5) <publisher> The publisher is currently defined as the entity that
>> published the dataset. If we were to issue DOIs for datasets from
>> FLOSSmetrics, for example, then the publisher would be FLOSSmetrics.
>> 6) <creationDate> and <publicationDate> are the same in this case;  
>> as I
>> understand it, the FLOSSmole data are created and then promptly  
>> published,
>> so there's not much point of differentiation. We can choose to use  
>> one or
>> the other, or both.
>> 7) <description> The description shown here is the short abstract  
>> on the
>> eprints record.
>> 8) <publicationPlace> is currently listed as SourceForge.net but  
>> could just
>> as appropriately be listed as Elon, NC.
>> 9) <discipline> is currently listed as softwareEngineering. The  
>> field is
>> intended to identify a scientific discipline in the most  
>> traditional sense;
>> this was what we thought made the most sense.
>> [4] Sample XML record
>> <?xml version="1.0"?>
>> <resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";  
>> xsi:noNamespaceSchemaLocation="std-doi.xsd">
>> <DOI>10.4118/flossmole.fmProjectAuthors2008-May</DOI>
>> <resourceIdentifiers>
>> <resourceIdentifier type="ProprietaryIdentifier">http://flosspapers.org/1585/ 
>> </resourceIdentifier>
>> <resourceIdentifier type="ProprietaryIdentifier">http://downloads.sourceforge.net/ossmole/fmProjectAuthors2008-May.txt.bz2 
>> </resourceIdentifier>
>> </resourceIdentifiers>
>> <creator>Megan@...</creator>
>> <creator>Kevin@...</creator>
>> <creator>James@...</creator>
>> <contributor>freshmeat</contributor>
>> <publisher>FLOSSmole</publisher>
>> <title>fmProjectAuthors2008-May.txt.bz2</title>
>> <language>en</language>
>> <structuralType>Digital</structuralType>
>> <mode>Abstract</mode>
>> <resourceType>Dataset</resourceType>
>> <registrationAgency>10.4118</registrationAgency>
>> <issueNumber>1</issueNumber>
>> <creationDate>2002-09-17</creationDate>
>> <publicationDate>2008-05-06</publicationDate>
>> <description>Freshmeat project authorship data.</description>
>> <publicationPlace>SourceForge.net</publicationPlace>
>> <size>
>> <value>486672</value>
>> <unit>Bytes</unit>
>> </size>
>> <format>text/plain</format>
>> <edition>1</edition>
>> <discipline>softwareEngineering</discipline>
>> </resource>
>>
>> Andrea Wiggins
>> PhD Student, School of Information Studies
>> Syracuse University
>> 337 Hinds Hall
>> Syracuse, NY 13244
>> awiggins@...
>> http://www.andreawiggins.com
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San  
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the  
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source  
>> participation
>> -Receive a $600 discount off the registration fee with the source  
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Ossmole-discuss mailing list
>> Ossmole-discuss@...
>> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss
>>
>>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss


Kevin Crowston
Syracuse University                            		Phone:  +1 (315)  
443-1676
School of Information Studies			Fax:    +1 (866) 265-7407
348 Hinds Hall						Web:    http://crowston.syr.edu/
Syracuse, NY   13244-4100   USA

*PS: The attachment named "PGP.sig" of type "application/pgp- 
signature" is an electronic signature that may be used to verify that  
this email came from me if you have PGP or GPG. Otherwise, you may  
safely ignore the attachment.

Re: [Ossmole-discuss] FLOSSmole DOIs

[Megan Squire <mconklin@el...>]

Andrea (and moles) This seems reasonable. I think keeping the
publication place as sourceforge is ok. This stuff is very confusing
to me - since it's not traditional publishing we just have to guess on
a lot of it.

Which of the resource identifiers do you think will end up in our DOAP
file, or will we use many/all of them?

-megan

On Fri, Feb 20, 2009 at 9:02 AM, Andrea Wiggins <awiggins@...> wrote:
> Hello all -
> We've gotten the go-ahead to start assigning DOIs[1] to data sets! More
> precisely, Syracuse University is now an authorized DOI publication agent
> via TIB [2], the registration agency for scientific primary and secondary
> data, which is operated by the German national library of science and
> technology. The reason to do this is that it allows better data citations
> and serves as a permanent identifier.
> The process of assigning DOIs to data sets involves resolving a few metadata
> ambiguities, so I wanted to check with the FLOSSmole user community for any
> suggestions before we finalize the details. Please feel free to make
> suggestions for the 9 fields [3] that are up for consideration; the rest are
> either fixed or completely unambiguous.  Below, I've pasted in an example
> XML file for a FLOSSmole dataset DOI definition [4].
>  There aren't necessarily any right answers here, so any feedback on the
> proposed DOI naming convention and metadata values would be very helpful.
> Thanks for your feedback!
> Andrea
>
> [1] http://www.doi.org
> [2] http://www.std-doi.de/front_content.php
> [3] Fields that are up for discussion:
> 1) <DOI> - everything after the 10.4118/ is up to us. The naming convention
> I've suggested below uses the repository name as a prefix (flossmole)
> followed by the filename, separated by a dot. This is by no means the best
> DOI convention, just what occurred to me as reasonably logical. We can also
> just assign ascending numeric values, e.g. 10.4118/floss.000001, as they do
> not have to be human-readable.
> 2) <resourceIdentifier> I've included the eprints record and data set
> download URLs as additional identifiers. They are shown as
> "ProprietaryIdentifiers" because URL is not a legal type for the field (URN
> would be, but these are not URNs, strictly speaking).
> 3) <creator> Currently Kevin, Megan and James are credited as creators, as
> they are the PI's for the FLOSSmole project.
> 4) <contributor> The contributor is currently defined as the source
> repository from which FLOSSmole spidered the data.
> 5) <publisher> The publisher is currently defined as the entity that
> published the dataset. If we were to issue DOIs for datasets from
> FLOSSmetrics, for example, then the publisher would be FLOSSmetrics.
> 6) <creationDate> and <publicationDate> are the same in this case; as I
> understand it, the FLOSSmole data are created and then promptly published,
> so there's not much point of differentiation. We can choose to use one or
> the other, or both.
> 7) <description> The description shown here is the short abstract on the
> eprints record.
> 8) <publicationPlace> is currently listed as SourceForge.net but could just
> as appropriately be listed as Elon, NC.
> 9) <discipline> is currently listed as softwareEngineering. The field is
> intended to identify a scientific discipline in the most traditional sense;
> this was what we thought made the most sense.
> [4] Sample XML record
> <?xml version="1.0"?>
> <resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation="std-doi.xsd">
> <DOI>10.4118/flossmole.fmProjectAuthors2008-May</DOI>
> <resourceIdentifiers>
> <resourceIdentifier type="ProprietaryIdentifier">http://flosspapers.org/1585/</resourceIdentifier>;
> <resourceIdentifier type="ProprietaryIdentifier">http://downloads.sourceforge.net/ossmole/fmProjectAuthors2008-May.txt.bz2</resourceIdentifier>;
> </resourceIdentifiers>
> <creator>Megan@...</creator>
> <creator>Kevin@...</creator>
> <creator>James@...</creator>
> <contributor>freshmeat</contributor>
> <publisher>FLOSSmole</publisher>
> <title>fmProjectAuthors2008-May.txt.bz2</title>
> <language>en</language>
> <structuralType>Digital</structuralType>
> <mode>Abstract</mode>
> <resourceType>Dataset</resourceType>
> <registrationAgency>10.4118</registrationAgency>
> <issueNumber>1</issueNumber>
> <creationDate>2002-09-17</creationDate>
> <publicationDate>2008-05-06</publicationDate>
> <description>Freshmeat project authorship data.</description>
> <publicationPlace>SourceForge.net</publicationPlace>
> <size>
> <value>486672</value>
> <unit>Bytes</unit>
> </size>
> <format>text/plain</format>
> <edition>1</edition>
> <discipline>softwareEngineering</discipline>
> </resource>
>
> Andrea Wiggins
> PhD Student, School of Information Studies
> Syracuse University
> 337 Hinds Hall
> Syracuse, NY 13244
> awiggins@...
> http://www.andreawiggins.com
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss
>
>

[Ossmole-discuss] FLOSSmole DOIs

[Andrea Wiggins <awiggins@sy...>]

Hello all -

We've gotten the go-ahead to start assigning DOIs[1] to data sets!  
More precisely, Syracuse University is now an authorized DOI  
publication agent via TIB [2], the registration agency for scientific  
primary and secondary data, which is operated by the German national  
library of science and technology. The reason to do this is that it  
allows better data citations and serves as a permanent identifier.

The process of assigning DOIs to data sets involves resolving a few  
metadata ambiguities, so I wanted to check with the FLOSSmole user  
community for any suggestions before we finalize the details. Please  
feel free to make suggestions for the 9 fields [3] that are up for  
consideration; the rest are either fixed or completely unambiguous.   
Below, I've pasted in an example XML file for a FLOSSmole dataset DOI  
definition [4].

  There aren't necessarily any right answers here, so any feedback on  
the proposed DOI naming convention and metadata values would be very  
helpful.

Thanks for your feedback!

Andrea


[1] http://www.doi.org

[2] http://www.std-doi.de/front_content.php

[3] Fields that are up for discussion:
1) <DOI> - everything after the 10.4118/ is up to us. The naming  
convention I've suggested below uses the repository name as a prefix  
(flossmole) followed by the filename, separated by a dot. This is by  
no means the best DOI convention, just what occurred to me as  
reasonably logical. We can also just assign ascending numeric values,  
e.g. 10.4118/floss.000001, as they do not have to be human-readable.
2) <resourceIdentifier> I've included the eprints record and data set  
download URLs as additional identifiers. They are shown as  
"ProprietaryIdentifiers" because URL is not a legal type for the field  
(URN would be, but these are not URNs, strictly speaking).
3) <creator> Currently Kevin, Megan and James are credited as  
creators, as they are the PI's for the FLOSSmole project.
4) <contributor> The contributor is currently defined as the source  
repository from which FLOSSmole spidered the data.
5) <publisher> The publisher is currently defined as the entity that  
published the dataset. If we were to issue DOIs for datasets from  
FLOSSmetrics, for example, then the publisher would be FLOSSmetrics.
6) <creationDate> and <publicationDate> are the same in this case; as  
I understand it, the FLOSSmole data are created and then promptly  
published, so there's not much point of differentiation. We can choose  
to use one or the other, or both.
7) <description> The description shown here is the short abstract on  
the eprints record.
8) <publicationPlace> is currently listed as SourceForge.net but could  
just as appropriately be listed as Elon, NC.
9) <discipline> is currently listed as softwareEngineering. The field  
is intended to identify a scientific discipline in the most  
traditional sense; this was what we thought made the most sense.

[4] Sample XML record
<?xml version="1.0"?>
<resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";  
xsi:noNamespaceSchemaLocation="std-doi.xsd">
	<DOI>10.4118/flossmole.fmProjectAuthors2008-May</DOI>
	<resourceIdentifiers>
		<resourceIdentifier type="ProprietaryIdentifier">http://flosspapers.org/1585/ 
</resourceIdentifier>
		<resourceIdentifier type="ProprietaryIdentifier">http://downloads.sourceforge.net/ossmole/fmProjectAuthors2008-May.txt.bz2 
</resourceIdentifier>
	</resourceIdentifiers>
	<creator>Megan@...</creator>
	<creator>Kevin@...</creator>
	<creator>James@...</creator>
	<contributor>freshmeat</contributor>
	<publisher>FLOSSmole</publisher>
	<title>fmProjectAuthors2008-May.txt.bz2</title>
	<language>en</language>
	<structuralType>Digital</structuralType>
	<mode>Abstract</mode>
	<resourceType>Dataset</resourceType>
	<registrationAgency>10.4118</registrationAgency>
	<issueNumber>1</issueNumber>
	<creationDate>2002-09-17</creationDate>
	<publicationDate>2008-05-06</publicationDate>
	<description>Freshmeat project authorship data.</description>
	<publicationPlace>SourceForge.net</publicationPlace>
	<size>
		<value>486672</value>
		<unit>Bytes</unit>
	</size>
	<format>text/plain</format>
	<edition>1</edition>
	<discipline>softwareEngineering</discipline>
</resource>


Andrea Wiggins
PhD Student, School of Information Studies
Syracuse University

337 Hinds Hall
Syracuse, NY 13244
awiggins@...
 http://www.andreawiggins.com

Re: [Ossmole-discuss] generating DOAP, a few questions

[Andrea Wiggins <awiggins@sy...>]

Regarding the customizability of the DOAP output, it looks like the  
ASF has included at least one custom field (for category) in their  
DOAP: http://projects.apache.org/guidelines.html

In general, metadata standards like DOAP are the sort of thing to  
modify as little as possible, but it is certainly reasonable to add a  
couple of custom fields. I'm wondering if we can integrate any of the  
documentation that Megan mentions into the FLOSSpapers.org metadata  
records for the datasets; I'm sure I haven't captured it all.

Megan, when you say that they would be for each project, each  
repository, each datasource_id, is that combinatorial or additive? If  
there are x projects, y repositories, and z datasource_ids, does it  
yield x*y*z files, or x+y+z files? It would make a difference with  
respect to how the dataset DOIs might fit in. (more on that before long)

Andrea

On Feb 18, 2009, at 5:41 PM, Kevin Crowston wrote:

> One other item you might include is the DOIs we're going to start
> assigning to datasets.
>
> Kevin Crowston
>
> On 18-Feb-09, at 12:02 PM, Megan Squire <mconklin@...> wrote:
>
>> Dear moles,
>>
>> I have been working on spitting out DOAP for our projects for one
>> weekend or so, and I'm running into a few questions. If it's ok with
>> you guys, I'd love to get feedback on my approach and corrections to
>> make it better. There are numerous of you who've volunteered in some
>> capacity to generate or consume our DOAP, or contribute your own, so
>> I'm hoping this conversation can represent a solid beginning for
>> getting this started officially.
>>
>> I'll outline some of my thoughts below. If you could correct me and
>> set me on the right track, I'd appreciate it.
>>
>> 1. I'd like to generate DOAP files for each of our projects, for each
>> of our repositories, for each datasource_id (collection date). I
>> envision these being consumed by the general public from the  
>> flossmole
>> public web presence. To me, these are "just another file format" -
>> right now we distribute datamarts (sql creates and inserts) and flat
>> file dumps of the data for a given "run" or "collection" date - so
>> DOAP files will be just another format to release every month.
>>
>> 2. My understanding is that I can release these files following a  
>> DOAP
>> format, such as the one found here:
>> http://www.ibm.com/developerworks/xml/library/x-osproj3/
>>
>> ...or on doapspace. (Whoops, I tried to link to doapspace but I'm
>> getting an error message that they've moved web hosts and the files
>> are not available. For those who were familiar with doapspace, the
>> link I was tryign to use was this one:
>> http://doapspace.org/doap/sf/ossmole - as an example)
>>
>> 3. I am pretty confident about how to fill all the fields shown  
>> (let's
>> use the IBM example for now) from <name> down using flossmole data we
>> already have, except I am not sure how to fill in the first three
>> lines - the part where it says <Project xmlns...>. Dumb question, but
>> can someone explain to me what should go here?
>>
>> 4. Also, I am not sure about flossmole-specific fields, or if that is
>> related to #3 above. For example, I'd like to add a field that tells
>> what datasource_id I am generating this file based on. I'd like to  
>> add
>> some other fields indicating who scraped the data, what repository or
>> donation it came from, etc. Any ideas for what is the proper DOAP way
>> to do this? What is "the DOAP way" to indicate the provenance of the
>> data inside the RDF file?
>>
>> 5. Assuming I've made a bunch of DOAP files, where do they live? I
>> guess I put them on a public-facing web site, but do they live there
>> forever, and do they get overwritten with new ones, or do I save them
>> and write new ones into a new place every month? We should assume we
>> collect new data on these projects every few weeks. Where does the  
>> new
>> file go? How do I link the files together so that a person can follow
>> the history of a project?
>>
>> 6. I don't think I need any libraries or fancy generators. Do I? I
>> mean, I can read the DOAP format (for example the IBM file shown  
>> above
>> or the doapspace examples), I can match the things in the example to
>> the stuff we have in the database, add any new fields that we decide
>> to add based on the answers to #4 above, and generate text files, and
>> post them on the web at a location we decide based on #5 above.
>>
>> Am I missing something? (Highly likely!)
>>
>> It would be great if someone could reply to the list, and be specific
>> in the answers so we can all learn and stay on the same page with how
>> this stuff works. Once we get it going for flossmole, I'm happy to
>> document the entire thing so that others can learn from our efforts,
>> and we can actually begin to swap DOAP back and forth with the
>> repositories and other collection projects similar to ourselves.
>>
>> -megan
>>
>> ---
>> ---
>> ---
>> ---------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source
>> participation
>> -Receive a $600 discount off the registration fee with the source
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Ossmole-discuss mailing list
>> Ossmole-discuss@...
>> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss

Andrea Wiggins
PhD Student, School of Information Studies
Syracuse University

337 Hinds Hall
Syracuse, NY 13244
awiggins@...
 http://www.andreawiggins.com

Re: [Ossmole-discuss] generating DOAP, a few questions

[Kevin Crowston <crowston@is...>]

One other item you might include is the DOIs we're going to start  
assigning to datasets.

Kevin Crowston

On 18-Feb-09, at 12:02 PM, Megan Squire <mconklin@...> wrote:

> Dear moles,
>
> I have been working on spitting out DOAP for our projects for one
> weekend or so, and I'm running into a few questions. If it's ok with
> you guys, I'd love to get feedback on my approach and corrections to
> make it better. There are numerous of you who've volunteered in some
> capacity to generate or consume our DOAP, or contribute your own, so
> I'm hoping this conversation can represent a solid beginning for
> getting this started officially.
>
> I'll outline some of my thoughts below. If you could correct me and
> set me on the right track, I'd appreciate it.
>
> 1. I'd like to generate DOAP files for each of our projects, for each
> of our repositories, for each datasource_id (collection date). I
> envision these being consumed by the general public from the flossmole
> public web presence. To me, these are "just another file format" -
> right now we distribute datamarts (sql creates and inserts) and flat
> file dumps of the data for a given "run" or "collection" date - so
> DOAP files will be just another format to release every month.
>
> 2. My understanding is that I can release these files following a DOAP
> format, such as the one found here:
> http://www.ibm.com/developerworks/xml/library/x-osproj3/
>
> ...or on doapspace. (Whoops, I tried to link to doapspace but I'm
> getting an error message that they've moved web hosts and the files
> are not available. For those who were familiar with doapspace, the
> link I was tryign to use was this one:
> http://doapspace.org/doap/sf/ossmole - as an example)
>
> 3. I am pretty confident about how to fill all the fields shown (let's
> use the IBM example for now) from <name> down using flossmole data we
> already have, except I am not sure how to fill in the first three
> lines - the part where it says <Project xmlns...>. Dumb question, but
> can someone explain to me what should go here?
>
> 4. Also, I am not sure about flossmole-specific fields, or if that is
> related to #3 above. For example, I'd like to add a field that tells
> what datasource_id I am generating this file based on. I'd like to add
> some other fields indicating who scraped the data, what repository or
> donation it came from, etc. Any ideas for what is the proper DOAP way
> to do this? What is "the DOAP way" to indicate the provenance of the
> data inside the RDF file?
>
> 5. Assuming I've made a bunch of DOAP files, where do they live? I
> guess I put them on a public-facing web site, but do they live there
> forever, and do they get overwritten with new ones, or do I save them
> and write new ones into a new place every month? We should assume we
> collect new data on these projects every few weeks. Where does the new
> file go? How do I link the files together so that a person can follow
> the history of a project?
>
> 6. I don't think I need any libraries or fancy generators. Do I? I
> mean, I can read the DOAP format (for example the IBM file shown above
> or the doapspace examples), I can match the things in the example to
> the stuff we have in the database, add any new fields that we decide
> to add based on the answers to #4 above, and generate text files, and
> post them on the web at a location we decide based on #5 above.
>
> Am I missing something? (Highly likely!)
>
> It would be great if someone could reply to the list, and be specific
> in the answers so we can all learn and stay on the same page with how
> this stuff works. Once we get it going for flossmole, I'm happy to
> document the entire thing so that others can learn from our efforts,
> and we can actually begin to swap DOAP back and forth with the
> repositories and other collection projects similar to ourselves.
>
> -megan
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss

Re: [Ossmole-discuss] DDB access

[James Howison <james@ho...>]

Great.  I've contacted the DBA.

Do feel obligated to report back to the list when you make a  
publication using the data; that helps us with NSF and other project  
sponsors.  That goes for everyone!

Yes, that's right, I said "feel obligated", rather than "feel free" :)

And please let us know if parts of the database are confusing, I know  
they are but we need input to rationalize things.

--J

On 18 Feb 2009, at 10:03 AM, Massimiliano Gambardella wrote:

> Hi all,
>
> me too I'm currently working on a research project concerning the  
> FLOSS
> project and the dynamics inside the developers' team.
> I'd like to request a DDB access, my preferred username is:  
> mgambardella
>
> Thanks,
> Massimiliano
>
> -- 
> Massimiliano GAMBARDELLA
> PhD Candidate
> University of Paris X - EconomiX & Orange Labs
> 200, Avenue de la République
> 92001 Nanterre Cedex, France
> Bâtiment K, Bureau 112
> Tel&Fax: +33 (0) 1 40 97 59 07
> e-mail: massimiliano.gambardella@...
> Web: http://economix.u-paris10.fr/fr/membres/?id=864
> Linux User n. 242535 (http://counter.li.org/)
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H_______________________________________________
> Ossmole-discuss mailing list
> Ossmole-discuss@...
> https://lists.sourceforge.net/lists/listinfo/ossmole-discuss

[Ossmole-discuss] generating DOAP, a few questions

[Megan Squire <mconklin@el...>]

Dear moles,

I have been working on spitting out DOAP for our projects for one
weekend or so, and I'm running into a few questions. If it's ok with
you guys, I'd love to get feedback on my approach and corrections to
make it better. There are numerous of you who've volunteered in some
capacity to generate or consume our DOAP, or contribute your own, so
I'm hoping this conversation can represent a solid beginning for
getting this started officially.

I'll outline some of my thoughts below. If you could correct me and
set me on the right track, I'd appreciate it.

1. I'd like to generate DOAP files for each of our projects, for each
of our repositories, for each datasource_id (collection date). I
envision these being consumed by the general public from the flossmole
public web presence. To me, these are "just another file format" -
right now we distribute datamarts (sql creates and inserts) and flat
file dumps of the data for a given "run" or "collection" date - so
DOAP files will be just another format to release every month.

2. My understanding is that I can release these files following a DOAP
format, such as the one found here:
http://www.ibm.com/developerworks/xml/library/x-osproj3/

...or on doapspace. (Whoops, I tried to link to doapspace but I'm
getting an error message that they've moved web hosts and the files
are not available. For those who were familiar with doapspace, the
link I was tryign to use was this one:
http://doapspace.org/doap/sf/ossmole - as an example)

3. I am pretty confident about how to fill all the fields shown (let's
use the IBM example for now) from <name> down using flossmole data we
already have, except I am not sure how to fill in the first three
lines - the part where it says <Project xmlns...>. Dumb question, but
can someone explain to me what should go here?

4. Also, I am not sure about flossmole-specific fields, or if that is
related to #3 above. For example, I'd like to add a field that tells
what datasource_id I am generating this file based on. I'd like to add
some other fields indicating who scraped the data, what repository or
donation it came from, etc. Any ideas for what is the proper DOAP way
to do this? What is "the DOAP way" to indicate the provenance of the
data inside the RDF file?

5. Assuming I've made a bunch of DOAP files, where do they live? I
guess I put them on a public-facing web site, but do they live there
forever, and do they get overwritten with new ones, or do I save them
and write new ones into a new place every month? We should assume we
collect new data on these projects every few weeks. Where does the new
file go? How do I link the files together so that a person can follow
the history of a project?

6. I don't think I need any libraries or fancy generators. Do I? I
mean, I can read the DOAP format (for example the IBM file shown above
or the doapspace examples), I can match the things in the example to
the stuff we have in the database, add any new fields that we decide
to add based on the answers to #4 above, and generate text files, and
post them on the web at a location we decide based on #5 above.

Am I missing something? (Highly likely!)

It would be great if someone could reply to the list, and be specific
in the answers so we can all learn and stay on the same page with how
this stuff works. Once we get it going for flossmole, I'm happy to
document the entire thing so that others can learn from our efforts,
and we can actually begin to swap DOAP back and forth with the
repositories and other collection projects similar to ourselves.

-megan

Re: [Ossmole-discuss] DDB access

[Massimiliano Gambardella <massimiliano.gambardella@gm...>]

Hi all,

me too I'm currently working on a research project concerning the FLOSS
project and the dynamics inside the developers' team.
I'd like to request a DDB access, my preferred username is: mgambardella

Thanks,
Massimiliano

-- 
Massimiliano GAMBARDELLA
PhD Candidate
University of Paris X - EconomiX & Orange Labs
200, Avenue de la République
92001 Nanterre Cedex, France
Bâtiment K, Bureau 112
Tel&Fax: +33 (0) 1 40 97 59 07
e-mail: massimiliano.gambardella@...
Web: http://economix.u-paris10.fr/fr/membres/?id=864
Linux User n. 242535 (http://counter.li.org/)

[Ossmole-discuss] DDB access

[Guido Conaldi <guido.conaldi@po...>]

Hi all,

I am currently working on a research project on the structural
dimensions of social processes influencing the production of FLOSS.
I'd like to request a DDB access, my preferred username is fipm.

thanks,
guido

-- 
Guido Conaldi
Assistant Post-doc
Institute of Management - University of Lugano
Via Giuseppe Buffi, 13
CH-6904 Lugano, Switzerland
Office Phone: +41 (0)58 666 4479

[Ossmole-discuss] DDB access

[Pau Minoves <pau.minoves@gm...>]

Hi,

I'm currently doing some research on open source software engineering.
I found your project and i think it would be perfect for me at this
stage, where i have to select some FOSS projects given some
characteristics.

May i have DDB access?
Thanks,

best,
Pau