Erika's homework update

[erika-b]

I'm having issues with the ContentDM cloning--the initial commit is running into an error during the "build with Jekyll" stage and none of the edits I do to _config.yml have helped. Exact error message is: /usr/local/bundle/gems/safe_yaml-1.0.5/lib/safe_yaml/load.rb:143:in `parse': (/github/workspace/./_config.yml): did not find expected key while parsing a block mapping at line 15 column 1 (Psych::SyntaxError)

• Repo: https://github.com/erika-b/tchp_dev
• Site: https://erika-b.github.io/tchp_dev/

My initial trial with the GH demo site/data worked really well!:

• Repo: https://github.com/erika-b/dhsi2022
• Site: https://erika-b.github.io/dhsi2022/

[evanwill]

Sorry @erika-b I forgot to mention a few things about CB-CDM in class!

Because CB-CDM uses plugins, it can not be built using the automatic GitHub Pages build. Instead, you will have to add a GitHub Action to deploy it:

• First, go into Settings > Pages, and for branch select "none", and save to turn off github pages.
• Next, follow the CB GitHub Actions docs to add the build action. You just have to create a new file, paste the content in, and commit.

However... that doesn't seem to be the build error your repository is encountering right now! It looks like the "_config.yml" is corrupted some how-- I will take a look!

[dcnb]

Hi Erika, So, I think the problem is that when you uncommented the noindex variable at line 78 in the _config.yml file, you didn't get rid of the space there -- once I got rid of that, I was able to get the site to build. Your CONTENDdm ul and collection-id are also not working though -- I think I got that -- the Colleciton Settings portion should be as follows: ########## # COLLECTION SETTINGS # # Set the metadata for your collection (the name of the csv file in your _data directory that describes the objects in your collection) # Use the filename of your CSV **without** the ".csv" extension! E.g. _data/demo-metadata.csv --> "demo-metadata" metadata: tchp_metadata # contentdm collection name, matches collection ID used by CDM cdm-collection-id: tacomacomm # CONTENTdm server url cdm-url: https://digitalcollections.lib.washington.edu/ You also have some extra lines in your metadata file that you should just delete (and the last record seems odd -- might look at that. But if you fix the above in the config.yml file, you should get it to work. BUT you'll need to use a github action or third party to get it live on the web right now -- see evan's note and mine below. We should also have mentioned this -- and Evan just did -- but CollectionBuilder-CONTENTdm does not work directly with GitHub pages. You can add a GitHub action to make it work: https://collectionbuilder.github.io/cb-docs/docs/deploy/actions/ Or you can also try just deploying it via a third party service. I'd recommend Render: https://collectionbuilder.github.io/cb-docs/docs/deploy/thirdparty/ If you go the Render route, which I think is easier, the static site address would be at a different url --- something like tchp_dev.onrender.com GitHub actions are really powerful though, and it's not a terrible idea to start working with them. Cheers! Devin

…

On Mon, Jun 6, 2022 at 4:15 PM erika b ***@***.***> wrote: I'm having issues with the ContentDM cloning--the initial commit is running into an error during the "build with Jekyll" stage and none of the edits I do to _config.yml have helped. Exact error message is: /usr/local/bundle/gems/safe_yaml-1.0.5/lib/safe_yaml/load.rb:143:in `parse': (/github/workspace/./_config.yml): did not find expected key while parsing a block mapping at line 15 column 1 (Psych::SyntaxError) - Repo: https://github.com/erika-b/tchp_dev - Site: https://erika-b.github.io/tchp_dev/ My initial trial with the GH demo site/data worked really well!: - Repo: https://github.com/erika-b/dhsi2022 - Site: https://erika-b.github.io/dhsi2022/ — Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTM4GKCOC6UIGB23GYBS4TVN2BALANCNFSM5YA7PSEA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[erika-b]

Woohoo thank you Evan and Devin! The documentation for github actions was super easy to follow and I have a site live. Now to clean up all that icky metadata 🤣