E. Lynette Rayle

**Implementation path of `in_work_ids`...** * `in_work_ids` calls `in_works` * which calls AF `ordered_by` * which executes a solr query: `"{!join from=proxy_in_ssi to=id}ordered_targets_ssim:#{id}"` As written, `in_work_ids` seems to be using solr...

Ran same relationship checks when relationship was setup using `members` instead of `ordered_members`. ``` parent_work1.member_ids # expected: [wk3] actual: [wk3] parent_work2.member_ids # expected: [wk3] actual: [wk3] parent_work1.ordered_member_ids # expected: []...

**Relationship Expectations** * child collections/works know about their parent collection through the `member_of_collection` relationship * parent works know about their child works/filesets through the `members` relationship **Expected method behaviors:** *...

My understanding from issue https://github.com/projecthydra-labs/hydra-pcdm/pull/66 was that related files was being postponed. Related object code was already in place and functional from PR https://github.com/projecthydra-labs/hydra-pcdm/pull/68. This behavior is inherited from Hydra::PCDM....

I like the idea of an indexer abstraction in Valkyrie. My thoughts on this... Having an abstraction allows Hyrax to write its indexers compliant with the Valkyrie indexer abstraction. Then...

@tpendragon I see there hasn't been much movement on this. Are there plans to move this forward?

@j-dornbusch I'm wondering if you can expand on the issue you are having with an example of a label that is not translating. Here are a few observations around language...

@geekscruff Can you take a look at this issue and comment on whether or not it still applies? I know there have been changes to the Getty processing since this...

Rather than remove the limit, I would be inclined to make it configurable. If the configured limit is nil, that can be used to effectively remove the limit. Change to...

I am not expecting this to be fixed in the next release of QA. I am leaving open in case we want to revisit this later.