Log of the #duraspace-ff channel on chat.freenode.net

Using timezone: Eastern Standard Time
* NIANLI joins12:43
* osmandin leaves12:47
<ruebot>awoods: ping12:54
* dwilcox leaves12:56
<awoods>ruebot: on a call
ruebot: I need to step away... is there something you have on your mind?13:18
* awoodsx joins13:20
<ruebot>awoods: question about test fixtures for upgration13:23
awoods: this https://github.com/Islandora-Labs/islandora/issues/16 && where we should put them if others want to use them. Dropbox, GitHub?
<awoods>ruebot: I have not read the whole thread... but GitHub sounds reasonable.13:25
<ruebot>i'll create an islandora-labs repo for now, and if we need to transfer it somewhere else, we can figure that out later.13:26
<awoods>ruebot: perfect
* dwilcox joins
* osmandin joins
* awoodsx leaves13:29
* awoodsx joins
* AndChat|563604 joins13:37
* awoodsx leaves13:41
* awoodsx joins14:31
* scossu joins14:32
* AndChat|563604 leaves14:35
* AndChat|563604 joins14:45
* awoodsx leaves
* awead joins
* awead_away leaves14:46
* awoodsx joins14:51
* AndChat|563604 leaves
* awoodsx leaves15:21
<awoods>ruebot: Where do things stand with the test data?15:25
* awoodsx joins
* awoodsx leaves15:26
<awoods>ruebot: ...I see: https://github.com/Islandora-Labs/upgration-test-fixtures/blob/master/README.md15:30
ruebot: although the actual data is somewhat not there.
ruebot: nm, the data is there in full force.15:31
ruebot: although I see objects... no datastreams?15:39
<ruebot>awoods: yeah, that was what i was curious about earlier. where should these live, and how exactly should we do an export.15:50
<awoods>ruebot: it looks like you did the export, no?
<ruebot>awoods: yep. looks like it is just the foxml.
<awoods>ruebot: are only the datastreams missing?
<ruebot>awoods: yep.15:51
<awoods>ruebot: it would be nice if the foxml and associated datastreams where in somewhere (like your GitHub) if a form that would be easy to then import them into a running F3.8
* dwilcox leaves15:52
<ruebot>awoods: maybe stupid question - what's the best way to get the datastreams? just copy them from the file system?
<awoods>mikeAtUVa ^^15:53
ksclarke ^^
<mikeAtUVa>ruebot: if you want a full lossless export use the context=archive when exporting.15:54
ruebot: it'll include base64-encoded datastreams in the XML.... so if there are big datastreams those will be HUGE XML files.
<ruebot>mikeAtUVa: ah. if that's the case, i get a nice ugly error in fedora admin15:57
<mikeAtUVa>ruebot, awoods: https://wiki.duraspace.org/display/FEDORA34/REST+API#RESTAPI-export
ruebot: what version of fedora?
<ruebot>mikeAtUVa: 3.8.0
mikeAtUVa: https://github.com/Islandora-Labs/islandora/issues/16#issuecomment-76236649 that's the error.
<awoods>ruebot: have you tried the REST API directly?15:58
<ruebot>awoods: not yet.
<mikeAtUVa>You can type it in a browser: objects/export?context=archive try that vs context=migrate to see if either works... (migrate has links to your repo for the datastream content)
<awoods>ruebot: maybe you need "bubble=true" ;)
ruebot: maybe you need "bubbles=true" ;)15:59
<ruebot>awoods: what is bubbles? other than a character on the wire or trailer park boys :-)
<awoods>ruebot: good question. I could make a joke, but there are too many options.16:00
* mikeAtUVa goes to test the export functionality on 3.8.0....16:04
<ruebot>whitescreen, and fedora.log gives me https://gist.github.com/ruebot/4fa2e1e94a558c7751c9
<mikeAtUVa>Looks broken to me too... works in 3.7.0...16:05
<ruebot>foo:8080/fedora/objects/yul:61282/export works fine.
<mikeAtUVa>awoods: maybe we need another 3 series release...
* ruebot cries
* awoods offers tissue16:06
mikeAtUVa: are you serious?
mikeAtUVa: be honest
<mikeAtUVa>awoods: about the release... probably not... it'd be easier to write a utility to export fedora 3 content.16:07
awoods: it's terribly unfortunate that the one major thing broken about the last fedora 3 release is the ability to losslessly export objects.
<ruebot>welp, i guess we're not getting any lossless test fixtures out of my repo :-(16:08
<awoods>mikeAtUVa: yes, there is something unfortunate about that.
<mikeAtUVa>ruebot... how big is the repo? There may be somewhat-less-easy ways to achive what you want.16:09
<awoods>mikeAtUVa: we need that capability, would you be willing to create a JIRA ticket?
<ruebot>mikeAtUVa: our repo is ~3T, ~215k objects
<mikeAtUVa>ruebot: you could export them using the default context, import them into another local fedora 3.7 installation and then export them from there...16:10
<dhlamb>><16:11
<mikeAtUVa>awoods: yeah... I'll write something up.16:12
<ruebot>mikeAtUVa: default context being the "migrate" context?
<dhlamb>ruebot: i can probably snag a few out of one of our vagrant environments. they're on 3.7. but we only have one or two per type of object16:13
<mikeAtUVa>reubot: yeah, though I haven't tested it in years, that was the purpose of that export context. (to copy from one online repo to another)
<ruebot>dhlamb: then we change the github issue from 5 to 2 :-)16:14
<dhlamb>rubot: right on
* dhlamb apologizes for just calling you "ru-boh"
<ruebot>mikeAtUVa: where do the datastreams go in that case?
dhlamb: well, if you stick to the french pronounciation, it would essentially be that anyway :-)16:15
<mikeAtUVa>mikeAtUva: in the exported foxml is has a resolvable URL to the original repository and when you import them (I think) it pulls the data from that URL to complete the new copy of the object.16:16
<dhlamb>ah, so that's the difference16:17
good to know
i've always had better luck with archive when going from fedora to fedora. that makes sense now.
<ruebot>https://github.com/Islandora-Labs/upgration-test-fixtures/blob/master/Export%20-%20Migrate/Audio/yul_61282.xml#L1874
<dhlamb>back in the dark times, before devops, at least. haven't touched that functionality in a long time until now
<ruebot>mikeAtUVa: that it?16:18
<mikeAtUVa>ruebot: yeah... but like dhlamb said... maybe it's flaky for migration... maybe it doesn't work if you need to authenticate or (in this case) if you're not running it from localhost.16:19
<ruebot>mikeAtUVa: cool. well, at least i have that cleared up for now.16:20
mikeAtUVa++
* awoods leaves16:24
* dhlamb leaves16:29
* acoburn leaves
* osmandin leaves16:34
* mikeAtUVa leaves17:06
* NIANLI leaves17:14
* awoods joins17:25
* ksclarke leaves18:20
* scossu leaves18:29
* awoods leaves18:51
* awoods joins19:00
* pivotal-bot_____ leaves19:27
* pivotal-bot_____ joins
* ksclarke joins20:28
* ksclarke leaves20:32
* ksclarke joins20:48
* awoods leaves21:13
* dhlamb joins21:30
* awoods joins21:42
* github-ff joins22:04
[fcrepo4] awoods pushed 1 new commit to master: http://git.io/xTcN
fcrepo4/master 5eb9636 osmandin: Change http error code for unauthorized PATCH request...
* github-ff leaves
* github-ff joins22:05
[fcrepo4] awoods closed pull request #738: Change http error code for unauthorized PATCH request (master...1379) http://git.io/AAll
* github-ff leaves
* travis-ci joins22:15
fcrepo4/fcrepo4#3436 (master - 5eb9636 : osmandin): The build passed.
Change view : https://github.com/fcrepo4/fcrepo4/compare/ed44bea426e9...5eb9636e19fa
Build details : http://travis-ci.org/fcrepo4/fcrepo4/builds/52371349
* travis-ci leaves
* dhlamb leaves23:23

Generated by Sualtam