initial commit of bookdown site

.gitignore

@@ -0,0 +1,6 @@
+.Rproj.user
+.Rhistory
+.RData
+_publish.R
+_book
+_bookdown_files

CODE_OF_CODUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in this class and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within class spaces and in public spaces when an individual is representing the class or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation may be further defined and clarified by maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting Vicky Rampin at [vicky dot rampin at nyu dot edu](mailto:vicky.rampin@nyu.edu). They will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. They are obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+## Contribute!
+If you'd like to contribute, that would be amazing! I will try my best to be on top of merge requests and issues. If you aren't comfortable with coding or git, you can email me ([vicky dot rampin at nyu dot edu](mailto:vicky.rampin@nyu.edu)) changes you'd like to see and I will open an issue for you or, if it's quick enough, make the change and give you attribution on this README.
+
+Here are some general instructions to help -- the following was adapted from [ProjectPorcupine's](https://github.com/TeamPorcupine/ProjectPorcupine)'s [CONTRIBUTING.md](https://github.com/TeamPorcupine/ProjectPorcupine/blob/master/CONTRIBUTING.md).
+
+Pease follow the [Contributor Covenant](CODE_OF_CONDUCT.md) in all your interactions with the project. If you would like to contribute to this project by modifying/adding to the code or data, please feel free to follow the standard GitLab workflow:
+
+1. Fork the project (the second button to the left under the title of the repo)
+2. Clone your fork to your computer.
+ * From the command line: `git clone https://gitlab.com/<USERNAME>/lis-628-data-librarianship.git`
+3. Change into your new project folder.
+ * From the command line: `cd lis-628-datalibrarianship`
+4. [optional]  Add the upstream repository to your list of remotes.
+ * From the command line: `git remote add upstream https://@gitlab.com:VickyRampin/lis-628-data-librarianship.git`
+5. Create a branch for your new feature.
+ * From the command line: `git checkout -b my-feature-branch-name`
+6. Make your changes.
+ * Avoid making changes to more files than necessary for your feature (i.e. refrain from combining your "real" pull request with incidental bug fixes). This will simplify the merging process and make your changes clearer.
+7. Commit your changes. From the command line:
+ * `git add <FILE-NAMES>`
+ * `git commit -m "A descriptive commit message"`
+8. While you were working some other changes might have gone in and break your stuff or vice versa. This can be a *merge conflict* but also conflicting behavior or code. Before you test, merge with main.
+ * `git fetch upstream`
+ * `git merge upstream/main`
+9. Test. Run the program and do something related to your feature/fix.
+10. Push the branch, uploading it to GitLab.
+  * `git push origin my-feature-branch-name`
+11. Make a "Merge Request" from your branch here on GitLab.
+
+### Best Practices for Contributing
+
+* Before you start coding, open an issue so that the community can discuss your change to ensure it is in line with the goals of the project and not being worked on by someone else. This allows for discussion and fine tuning of your feature and results in a more succent and focused additions.
+    * If you are fixing a small glitch or bug, you may make a MR without opening an issue.
+    * If you are adding a large feature, create an issue so that we may give you feedback and agree on what makes the most sense for the project before making your change and submitting a MR (this will make sure you don't have to do major changes down the line).
+
+* Merge Requests are eventually merged into the codebase. Please ensure they are:
+    * Well tested by the author. It is the author's job to ensure their code works as expected.
+
+* If your code is untested, log heavy, or incomplete, you can use GitLab's [Work In Progress (WIP) feature](https://docs.gitlab.com/ce/user/project/merge_requests/work_in_progress_merge_requests.html) on your merge request so others know it is still being tested and shouldn't be considered for merging yet. This way we can still give you feedback or help finalize the feature even if it's not ready for prime time.
+
+That's it! Thanks for your contribution!
+
+## Contact info
+
+You are welcome to email me at [vicky dot rampin at nyu dot edu](mailto:vicky.rampin@nyu.edu) if you have questions or concerns, or raise an issue on this repository and I will do my best to respond quickly!

README.md

@@ -1,2 +1,29 @@
-# LIS 628 Data Librarianship
+# LIS 628: Data Librarianship and Management
 
+[![forthebadge](https://forthebadge.com/images/badges/contains-cat-gifs.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/60-percent-of-the-time-works-every-time.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/cc-sa.svg)](https://forthebadge.com)
+
+A class for [Pratt SLIS](https://www.pratt.edu/academics/information/about-the-school/) by [Vicky Rampin](https://vicky.rampin.org).
+
+## Class description
+
+The world of data is seemingly a new frontier for libraries, yet in some ways, data and data sets are comparable to other print and electronic resources that librarians historically have been charged with locating, teaching, collecting, organizing, and preserving. This course asks how best we can serve the needs of a burgeoning community of data users/producers while meeting the new challenges that data present to our existing skillsets, workflows, and infrastructure. Topics will include data reference and literacy; archives and repositories; formats and standards; ethics and policy. Statistical/GIS software and research data management are also explored.
+
+## Build our book locally
+1. Fork, clone or download this project (See #1-4 in the 'Contribute!' section below).
+2. Install R & RStudio.
+3. Install the bookdown, RMarkdown, and tinytex packages in RStudio with the following two commands in the R terminal:
+	* `install.packages(c("rmarkdown", "bookdownplus", "tinytex", "webshot"))`
+	* `tinytex::install_tinytex()`
+	* `webshot::install_phantomjs()`
+
+	You can also click `Tools` > `Install Packages` and paste in the package names there (make sure "install dependencies" is checked) separated by commas, like so: `rmarkdown, bookdownplus, tinytex, webshot`.
+
+4. Go to the project folder and double click `lis-628-data-librarianship.Rproj` to start the project in RStudio.
+5. Run this command in the R Console after RStudio opens: `bookdown::render_book('index.Rmd', 'all')`
+6. Go to the folder `_book` in the project folder and click `index.html` to view the book locally in your browser.
+
+## Contribute!
+If you'd like to contribute, that would be amazing! I will try my best to be on top of merge requests and issues. Before you start, please refer to our [contributing guide](CONTRIBUTING.md). 
+
+## Contact info
+You are welcome to email me at [vicky dot rampin at nyu dot edu](mailto:vicky.rampin@nyu.edu) if you have questions or concerns, or raise an issue on this repository and I will do my best to respond quickly!

index.Rmd

@@ -0,0 +1,46 @@
+--- 
+title: "LIS 628 - Data Librarianship and Management"
+author: "Vicky Rampin"
+date: "Fall 2021"
+description: "Open educational resources for learning data management best practices"
+site: bookdown::bookdown_site
+colorlinks: yes
+favicon: imgs/favicon.ico
+documentclass: book
+always_allow_html: yes
+output:
+  bookdown::gitbook:
+    css: [style.css]
+    config:
+      toc:
+        before: |
+          <p><a href="">LIS 628 Data Librarianship</a></p>
+          <p>Pratt SLIS, Fall 2019</p>
+          <p>Instructor: <a href="https://vicky.rampin.org">Vicky Rampin</a></p>
+        after: |
+          <p><a href="https://gitlab.com/RLesur/bookdown-gitlab-pages" target="blank">Published with bookdown &amp; GitLab</a></p>
+          <p>Original content is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.</p>
+          <p>Any questions, contact: <a href="mailto:vicky.rampin@nyu.edu">vicky.rampin@nyu.edu</a></p>
+      edit: https://gitlab.com/VickyRampin/lis-628-datalibrarianship/edit/main/%s
+      search: yes
+      download: ["pdf", "epub"]
+      sharing: null
+  bookdown::pdf_book:
+    latex_engine: xelatex
+  bookdown::epub_book: default
+---
+
+# Welcome {-}
+
+Welcome to Data Librarianship and Management! In this class, I'm hoping to impart some practical skills, an understanding of best practices, and prepare you for a variety of data librarianship positions.
+
+On this site, you'll find the syllabus, materials for each class, and links to where you should submit assignments.
+
+![](imgs/lb-welcome.png)
+
+## Past Materials {-}
+
++ [2020 Fall Book - pdf](files/2020-fall-book.pdf), [2020 Fall Book - epub](files/2020-fall-book.epub), & [2020 Syllabus](files/2020-syllabus.pdf)
++ [2018 Fall Book - epub](files/2018-fall-book.epub) & [2018 Syllabus](files/2018-syllabus.pdf)
++ [2019 Fall Book - pdf](files/2019-fall-book.pdf), [2019 Fall Book - epub](files/2019-fall-book.epub), & [2019 Syllabus](files/2019-syllabus.pdf)
++ [2018 Fall Book - epub](files/2018-fall-book.epub) & [2018 Syllabus](files/2018-syllabus.pdf)

lis-628-data-librarianship.Rproj

@@ -0,0 +1,13 @@
+Version: 1.0
+
+RestoreWorkspace: Default
+SaveWorkspace: Default
+AlwaysSaveHistory: Default
+
+EnableCodeIndexing: Yes
+UseSpacesForTab: Yes
+NumSpacesForTab: 2
+Encoding: UTF-8
+
+RnwWeave: Sweave
+LaTeX: pdfLaTeX

style.css

@@ -0,0 +1,24 @@
+@import url('https://fonts.googleapis.com/css?family=Questrial');
+@import url('https://fonts.googleapis.com/css?family=Quattrocento');
+
+.book.font-family-1 {
+    font-family: 'Questrial', sans-serif;
+}
+
+.book.font-family-0 {
+  font-family: 'Quattrocento', serif;
+}
+
+.book .book-header, .book .book-summary {
+    font-family: 'Questrial', sans-serif;
+}
+
+.summary p{
+  padding-left: 0.8em;
+  padding-right: 0.2em;
+}
+
+
+.book .book-body .page-wrapper .page-inner section.normal table {
+  width:auto;
+}