Giter Club home page Giter Club logo

fair-phytoliths's Introduction

layout title nav_order permalink
default
Home
1
/

FAIR Phytoliths: Increasing the FAIRness of phytolith data

All Contributors

DOI

"We want to learn new ideas and new ways to share our work and then explain these ideas to the group of people working with old cells from green stuff" 🌱

This is what we do explained using only the 1000 most common words (produced with UP-GOER5 text editor).

Welcome!

Thanks for visiting the FAIR Phytoliths project! In this document you can find lots of information about this project. You can just scroll down or use the quick links below for each section.

What is this project about and why is it important?

Phytoliths are plant microfossils used world-wide to address a variety of questions in a variety of fields like archaeology, palaeoecology and palaeontology. Diverse laboratory procedures, analyses and identification criteria are used resulting from different research traditions. Some steps, such as the normalisation of nomenclature through the International Phytolith Society (IPS), have been promoted to standardise phytolith analysis and the subsequent publication of data. However, the standardisation of phytolith research and data publication is still far from being achieved. A recent assessment of the data sharing practices within the phytolith community (Karoune 2020) found that only half of the publications share some form of data and the majority do not provide reusable data.

FAIR Phytoliths has grown from initial efforts by Emma Karoune to raise awareness of issues with poor data sharing practice. This initiative is supported by the International Phytolith Society on data sharing and represents the first steps towards the FAIRification of phytolith data: an evaluation of sharing practices in phytolith research; the creation of a GitHub repository for collaborative use by this working group and the initiation of the FAIRification project; and the development of a webpage to provide the community with information as the project proceeds.

What do we want to do?

The outcomes expected from this project are:

  1. Promoting the use of GitHub as a collaborative workspace.
  2. Conduct a FAIR assessment of phytolith sharing data using two regional studies: Europe and South America.
  3. Gather information about data sharing practices, expectations and predisposition within the phytolith community via a survey.
  4. Designing a webpage to advertise and promote the project to the phytolith community and to gain contributors.
  5. Create a protocol for phytolith (raw) data publication and sharing.

The project is organised in three work packages:

1. FAIR assessment of existing data.

Published phytolith datasets from South America and Europe will be assessed to establish the breadth of phytolith data (including archaeological, palaeoecological and modern botanical studies). This will initially be from articles published between 2016 to 2020, but earlier data will be collected if needed to reach data saturation (Saunders et al. 2017). These two regions have been selected because different phytolith "traditions" exist among researchers working in Europe and South America. Most European phytolith studies use the standardised nomenclature (ICPN 1.0), whereas South American researchers have developed their own naming criteria. In spite of this, the overall principle of the methods used for processing phytolith samples is the same (the separation of phytoliths from other particles in sediments or modern plants), as well as the research questions addressed and the types of data analysis that is conducted on primary phytolith data, thus ensuring the comparability of the datasets. The FAIR assessment will be conducted by establishing a subject-specific FAIR assessment tool, similar to the FAIR enough? checklist, using a Google Form to standardise data collection.

2. Community building.

A survey will be sent out to our research community to gain insight into how researchers see their own data sharing practice. This will gather information about current data sharing practices and opinions on why more open practices are not used. This survey will give the option to the authors of the existing datasets to make their data open access. This also gives us the opportunity to work with researchers to improve these datasets in terms of their FAIRness. This could take the same approach as the "Bring your own data workshop" at the University of Cambridge that aimed to improve data management through training. These improved datasets will then be used as case studies to raise awareness of the need for planning data management and provide resources for more training in our community. Training our community in open science skills, such as GitHub, will help to aid accessibility to open science tools in general but also help to advance the implementation of future FAIR data criteria.

3. Development of guidelines for existing datasets and future FAIR phytolith data.

The FAIR assessment of existing practices and datasets will be used to propose criteria for minimum information requirements for data sharing and potential areas of reuse that consider the limitations of using these data. These constraints will be used to suggest best practice criteria for the implementation of future FAIR phytolith data.

What does this project need?

We need you! - This project relies on participation from the phytolith research community.

There are a number of ways that you can get involved:

  • Fill in our survey here.
  • Provide phytolith datasets from South American and European studies in which you participated.
  • Contact us about getting involved in community building or the development of the FAIR guidelines.

For detailed information, please read our contributor guidelines and code of conduct.

Who are we?

Our core team of contributors are (in alphabetical order): Juan JosΓ© GarcΓ­a-Granero, Emma Karoune, Carla Lancelotti, Marco Madella, Javier Ruiz-PΓ©rez.

Get in touch

Please feel free to get in touch with us by email at [email protected] or on twitter.

Find out more

We are achiving our presentations and other resources from this project under the Open Phytoliths Community on Zenodo - see this link here.

  • Project documents:

  • Relevant papers:

    • Zurro, D., Garcia-Granero, J.J., Lancelotti, C. and Madella, M. 2016. Directions in current and future phytolith research. Journal of Archaeological Science, 68: 112-117. DOI: 10.1016/j.jas.2015.11.014 - see here.
    • Karoune, E. 2020. Data from assessing open science practices in phytolith research. Journal of Open Archaeology Data, 8(1): 6. DOI: http://doi.org/10.5334/joad.67.
    • Karoune, E., 2022. Assessing Open Science Practices in Phytolith Research. Open Quaternary, 8(1), p.3. DOI: http://doi.org/10.5334/oq.88.
  • Conference presentations: Please see our presentations here.

  • Funding applications: Please see our funding applications here.

Thank you

Thanks for taking the time to read this project page and do please get involved!

Funding

This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 824087.

EOSC life

License:

Shield: CC BY 4.0

This work is licensed under a Creative Commons Attribution 4.0 International License.

CC BY 4.0

Contributors ✨

Thanks goes to these wonderful people (emoji key):


Em K

πŸ“– πŸ€” πŸ“† πŸ‘€

Javier

πŸ“– πŸ€” πŸ“† πŸ‘€

cl379

πŸ“– πŸ€” πŸ“† πŸ‘€

Esther Plomp

πŸ‘€

dancabanes

πŸ€”

Malvika Sharan

πŸ”

Marco m4bcn

πŸ“– πŸ€” πŸ“†

francesca-dagostini

⚠️

Carlos G. Santiago-Marrero

πŸ““

GCampbell10

πŸ”

This project follows the all-contributors specification. Contributions of any kind welcome! See the list of contributors here for detailed information about each of us!

fair-phytoliths's People

Contributors

allcontributors[bot] avatar cel31 avatar cl379 avatar ekaroune avatar hackmd-deploy avatar jruizperez avatar juanjogarciagranero avatar open-phytoliths-admin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

cel31

fair-phytoliths's Issues

FAIR guidelines

  • create guidelines for existing data
  • create guidelines for future data
  • Write paper for guidelines

Setting up community management

We need to decide how we are going to run our project and need to get a number of tasks done.

Let's have a discussion about these issues and start to work on them.

  • Set up slack account for communication
  • Set up gmail account for organisation
  • Setting up repository as organisation with organisation user details
  • README file with vision statement, open canvas, roadmap, contact details.
  • Code of conduct
  • Contributor guidelines
  • Set up twitter
  • Set up webpage
  • Make an advertising slide to use at conferences. Google slide
  • Authorship guidelines
  • setting up all contributors bot
  • adding contributors from funding and OLS3
  • Translation of readme in to spanish and other languages.

Add anything else to the list above that needs to be done.

FAIR assessment data collection methodology

Things to be done before data collection can start:

  • Discuss data collection method
  • Decide steps and clearly write down
  • Write down data categories in table
  • Set up google form
  • Trial of data categories and google form
  • Picking several articles to trial
  • Discussing trial
  • changing data categories
  • finalising google form

Writing data paper for FAIR assessment

  • finalise dataset
  • clean dataset
  • upload dataset to repository
  • Select journal for data paper - Scientific data, JOAD, Open research europe, data in brief, botanical studie?
  • Write data paper
  • Edit data paper
  • submit data paper
  • do revisions from peer review

Feedback on authorship guidelines

Email from Welmoed Out.

Github is @WelmoedO

The email included comments about authorship guidelines:

  • "the authorship guidelines are not clear to me. If one deposits a data set or code, does one become an author in the group open phytolith community or active contributor?

We need to make this more clear so that it is easier to understand the distinction between the different groups.

We also need to make it clear that we are currently not creating a repository so the data that can be offered to us is just for FAIR assessment of it as case studies for training the community.

For discussion at a meeting I think.

Onboarding of new community members

  • start onboarding folder/material
  • Finalised onboarding folder
  • add new community members to github repo
  • add new members to contributors list
  • Contact community members that have responded to the survey

Onboarding new post-doc - Celine Kerfant

Access to software and communications

  • add to slack channel
  • check access to google drive
  • access to Github
  • access to twitter

Training needs

  • Slack
  • Google drive
  • Hackmd
  • Github - basics
  • Github collaboration
  • Github project management
  • FAIR assessment methodology
  • general open science skills
  • R analysis

EOSC project infrastructure

Continued infrastructure needs:

  • Translation of readme in to spanish and other languages.
  • Project management board, milestones and issues

Add any other things to the list that are needed.

Github training

  • Create Github training resources
  • training for new core team
  • advertise Github training for new community members

Initial Infrastructure finalising

Checking infrastructure for start of EOSC project -

  • Set up slack account for communication
  • Set up gmail account for organisation
  • Setting up repository as organisation with organisation user details
  • README file with vision statement, open canvas, roadmap, contact details.
  • Code of conduct
  • Contributor guidelines
  • Set up twitter
  • Set up webpage
  • Make an advertising slide to use at conferences. Google slide
  • Authorship guidelines
  • setting up all contributors bot
  • adding contributors from funding and OLS3

All checked.

FAIR assessment training

  • training for initial datasets
  • training for new guidelines
  • make final training documentation and materials
  • archive training materials in Zenodo

FAIR assessment

  • Set up folders for data in google drive
  • Set up data management repo
  • Set up final google form for europe 2016-2020
  • Set up final google form for south america 2016-2020
  • Download publish or perish
  • Do google scholar search in PoP for Europe and South America and download csv to add to google drive folder
  • Start collecting articles and data collection
  • Generate google sheet for each form
  • Check we are all collecting in the same way - after one week
  • Download google sheet onto github repo at the end of every week as csv file
  • When finished google scholar list - check we have enough articles/data
  • Decide whether to collect more - extend by how many years?
  • Training for R analysis
  • Make sure that github repo is linked to Rstudio
  • Analyse data - create pipelines for data analysis in R of dataset
  • Create figures
  • check journal requirements for authors in terms of data requirements and also a data availability statements.

Analysis of community survey

  • creating personas and pathways for project from survey results.

  • analysing data using R

  • creating figures

  • writing paper on initial findings and ways forward/data sharing in archaeology/phytos/ community building.

Community survey

Here are all our thoughts about the survey:

  • Setting up google doc for question ideas. Google doc
  • Checking and finalising the questions
  • Making the google form and set up google sheet
  • Sending out the google form
  • Advertising the survey
  • Need to contact IPS to find out about mailing list, forum, etc - what is the size of their membership?
  • Make a list of all the phytolith labs and a contact for each one. Google sheet
  • Write blog for IPS website - for initiation of project and survey
  • Readvertising the survey to direct contacts and others from list created.
  • Advertising the survey at IMPR conference in sept 2021.
  • closing date of end of november
  • readvertise on twitter and sending emails before this date
  • Binalot talk at the Archaeological Studies Program on October 20th

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.