The
Problem
e
Hyrax
assumes
uniform
metadata
across
all
items
¢
Adding
a
metadata
field
requires
a
lot
of
code
changes
(=17
places)
The
Solution
®
Allows
admins
(not
just
developers)
to
customize
the
schema
and
metadata
of
their
collections
either
through
a
form
submission
or
profile
upload
®
Collections
of
the
same
repository
have
different
metadata
needs
and
this
gem
gives
them
the
flexibility
to
define
them
Julie
Allinson
AllinsonFlex
is
named
for
developer,
metadata
guru,
and
Community
superstar
Julie
Allinson.
This
work
is
part
of
the
tremendous
legacy
left
upon
Julie's
passing
in
May
2020.
Founded
on
her
prior
work
on
the
Dog
Biscuits
&
Houndstooth
gems,
Julie’s
work
on
this
gem
for
Indiana
University
was
a
passion
project.
Her
Notch8
and
IU
colleagues
are
proud
to
complete
it
in
her
memory.
<
Edit
Alinson
Flex
Protile
Metadata
Profile
——————»
Begin
by
adding
a
new
metadata
profile
=
Flexible
Metadata
Profiles
7
Flexible
Metadata
Profiles
=3
«¢—
Flexible
Metadata
Profiles
will
display
schema
version,
proile
version,
profile
type,
created
at,
and
options
Edit
Classes
(worktypes)
®
PagedResource
<
Edit
Alnson
Flex
Pratile
o
Scientific
i
—wT=Y
W
E
A=K
|
®
BibRecord
==
®
Image
T
P
Context
Definitions
e
Allows
you
to
connect
a
context
to
a
specific
collection
®
Field
definitions
can
be
applied
to
an
entire
collection
Property
Definitions
——————p»
Set
specific
public
labels
and
definitions,
cardinality,
default
values,
etc.
on
metadata
Are
you
ready
for
flexible
metadata?
Notch8
is
seeking
project
partners
to
implement
AllinsonFlex
and
to
sponsor
work
that
will
make
this
versatile
feature
even
better!
connect@notch8.com
The
Project
®
Sponsored
by
Indiana
University
®
ESS
Images
Hyrax
application
How
It
Works
The
gem
is
able
to
read
an
M3
schema
along
with
a
profile
YAML
file
and
provides
a
Ul
for
editing
the
classes,
contexts,
mappings
and
properties
within.
It
then
provides
hooks
to
the
various
pieces
of
Hyrax
and
similar
Rails
based
systems
to
in
order
to
assign
contexts
to
Admin
Sets,
create
and
modify
works
and
have
all
the
properties
of
that
work
defined
dynamically
by
users
during
run
time.
Work
Types
must
exists
in
code
(there
is
a
work
type
generator),
but
all
properties
within
can
be
edited
dynamically
by
the
library
and
are
stored
as
data.
Future
Goals
o
Admin-defined
(non-developer)
new
worktype
creation
e
Compatibility
with
Valkyrie
e
Multi-tenant
functionality
in
Hyku
e
Optimize
database
tables
for
speed
®
Improve
installation
workflow