Patrick Murray-John patrickmj

## DrsItemResponse.js
/*
 * This is an example single item API response, using the Image_Payload in this repo as a starting point.
 *
 * It merges how IIIf files and manifests are handled.
 *
 * It also includes simplified variations of the element names from XML. I think they align closely
 * enough with the XML version to be recognizable without losing semantics, at least for what CERES
 * needs.
 *
 * Elements below query and result are optional, unless otherwise noted (or if I don't get an HTTP 200 response,

## APIstructures.js
/*
 * First passes as possible API query and response structures
 * for various Northeastern Library DH projects
 *
 *
 *
 */
// Work / Item data
// /item/{id}

## blocksVariableDefinitions.js
// I've seen code for building WP blocks with JS like this

( function( blocks, editor, i18n, element) {
    var el = element.createElement;
    var __ = i18n.__;
    var RichText = editor.RichText;
  // do block things
  }(
    window.wp.blocks,
    window.wp.editor,

## gist:1cc0958ea913abf28736d7936ac71918
<!-- Save all this to wherever (copy-paste from the Raw code should work), the open it in a browser.

If there are problems, I'll move it to a real GitHub repo for issue reporting.
(It's had minimal testing)

-->

<html>
  <head>
    <script type='text/javascript'>

## manifest.json

{

    "@context": "http://iiif.io/api/presentation/2/context.json",
    "@id": "https://data.ucd.ie/api/img/manifests/ivrla:7173",
    "rendering": {
        "@id": "https://digital.ucd.ie/get/ivrla:7173/content",
        "format": "application/pdf",
        "label": "Download as PDF"
    },

## alto2txt.xslt
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
    xmlns:a="http://www.loc.gov/standards/alto/ns-v2#"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    version="1.0"
    >
<xsl:output method="text"/>
<xsl:strip-space elements="*"/>

    <xsl:template match="/">

## hello.rb
2.times do
  puts "Hello World"
end

## github_issues_to_csv_v3.rb
require 'octokit'
require 'csv'
require 'date'

# Description:
# Exports Github issues from one or more repos into CSV file formatted for import into JIRA
# Note: By default, all Github comments will be assigned to the JIRA admin, appended with
# a note indicating the Github user who added the comment (since you may not have JIRA users
# created for all your Github users, especially if it is a public/open-source project:
#

## github_issues_to_csv.rb
require 'json'
require 'open-uri'
require 'csv'
require 'date'

# Github credentials to access your private project
USERNAME="myusername"
PASSWORD="mypassword"

# Project you want to export issues from

## export_repo_issues_to_csv.py
"""
Exports Issues from a specified repository to a CSV file

Uses basic authentication (Github username + password) to retrieve Issues
from a repository that username has access to. Supports Github API v3.
"""
import csv
import requests
	/*
	* This is an example single item API response, using the Image_Payload in this repo as a starting point.
	*
	* It merges how IIIf files and manifests are handled.
	*
	* It also includes simplified variations of the element names from XML. I think they align closely
	* enough with the XML version to be recognizable without losing semantics, at least for what CERES
	* needs.
	*
	* Elements below query and result are optional, unless otherwise noted (or if I don't get an HTTP 200 response,
	/*
	* First passes as possible API query and response structures
	* for various Northeastern Library DH projects
	*
	*
	*
	*/
	// Work / Item data
	// /item/{id}
	// I've seen code for building WP blocks with JS like this

	( function( blocks, editor, i18n, element) {
	var el = element.createElement;
	var __ = i18n.__;
	var RichText = editor.RichText;
	// do block things
	}(
	window.wp.blocks,
	window.wp.editor,
	<!-- Save all this to wherever (copy-paste from the Raw code should work), the open it in a browser.

	If there are problems, I'll move it to a real GitHub repo for issue reporting.
	(It's had minimal testing)

	-->

	<html>
	<head>
	<script type='text/javascript'>

	{

	"@context": "http://iiif.io/api/presentation/2/context.json",
	"@id": "https://data.ucd.ie/api/img/manifests/ivrla:7173",
	"rendering": {
	"@id": "https://digital.ucd.ie/get/ivrla:7173/content",
	"format": "application/pdf",
	"label": "Download as PDF"
	},
	<?xml version="1.0" encoding="UTF-8"?>
	<xsl:stylesheet
	xmlns:a="http://www.loc.gov/standards/alto/ns-v2#"
	xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	version="1.0"
	>
	<xsl:output method="text"/>
	<xsl:strip-space elements="*"/>

	<xsl:template match="/">
	require 'octokit'
	require 'csv'
	require 'date'

	# Description:
	# Exports Github issues from one or more repos into CSV file formatted for import into JIRA
	# Note: By default, all Github comments will be assigned to the JIRA admin, appended with
	# a note indicating the Github user who added the comment (since you may not have JIRA users
	# created for all your Github users, especially if it is a public/open-source project:
	#
	require 'json'
	require 'open-uri'
	require 'csv'
	require 'date'

	# Github credentials to access your private project
	USERNAME="myusername"
	PASSWORD="mypassword"

	# Project you want to export issues from
	"""
	Exports Issues from a specified repository to a CSV file

	Uses basic authentication (Github username + password) to retrieve Issues
	from a repository that username has access to. Supports Github API v3.
	"""
	import csv
	import requests