# pidcache server configuration - getting the PIDs from
escidoc.pidcache.service.url=http://pubman.mpdl.mpg.de:8090/pidcache/handle
escidoc.pidcache.server=pubman.mpdl.mpg.de
escidoc.pidcache.user.name=pid_manager
#escidoc.pidcache.user.password=TGata67aiZIos
escidoc.pidcache.user.password=ga6FF63ddg
# the implementation used for the PIDProviderIf, use PIDProviderMock for testing purposes for not spending too much pids, use PIDProvider for
# live scenario
escidoc.pidprovider.class=de.mpg.escidoc.handler.PIDProvider
# the pubman instance registering handles for
escidoc.pubman.instance.url=http://pubman.mpdl.mpg.de
escidoc.pubman.instance.context.path=/pubman
escidoc.pubman.item.pattern=/item/$1
escidoc.pubman.component.pattern=/item/$1/component/$2/$3
# triplestore database configuration - used for item/component mapping
triplestore.datasource.url=jdbc:postgresql://localhost:5432/riTriples
triplestore.datasource.driverClassName=org.postgresql.Driver
triplestore.datasource.username=postgres
triplestore.datasource.password=postgres
# the table name of the item-component relation triplestore table
triplestore.datasource.component.table=t46
# the table name of the item-object pid relation triplestore table
triplestore.datasource.pid.table=t8
# set this property to force triplestore table update when modifiying object pids
triplestore.datasource.table.update=true